Shibboleth Developers

[Scott Cantor <>]

Before I read this in depth, I'd like to be sure that you guys know that
SAML 2.0 standardizes Single Logout, and that anything we do is likely going
to be based on that standard, not anything we would invent.

At a basic level, the issue is not "how do we do this?" It's fairly well
understood. It's how and when do we implement the standard way of doing
this? And more importantly, what facilities do we create for notifying
applications when these protocol flows for logout happen, and what's the
interface to authentication functions provided by arbitrary and proprietary
Web-ISO's so that the logout can be propagated across that boundary in both
directions?

-- Scott