Backchannel Notify and NameID bound sessions

[Cantor, Scott]

> When /Shibboleth.sso/Logout is called from one browser, the SP collects
> all sessions of the user based on the NameID and sends a SOAP message to
> the <Notify> target that contains all these sessions.

That's how a SAML logout works, depending on the SessionIndex in the message, but when the SP initiates a logout, it only initiates a logout of the session it's being told to handle. Unless there's a bug anyway, but the code I looked at appears to be sending back channel notification with only a single session.

> Can anyone give me a hint how to extend the example WSDL described at
> 
> https://wiki.shibboleth.net/confluence/display/SHIB2/SLOWebappAdaptation
> 
> in a way that all <SessionID>s are passed to
> 
> function LogoutNotification($SessionID)?

Are you talking about what the SP does, or are you talking about some example of an application processing the notify messages? If it's an example, it's just to work from, just change it however you want to. If there's a WSDL (which I didn't write), then if it's not consistent with the schema the SP uses, that would be wrong, obviously.

Basically, is the SP sending the right sessions to the notify hook, or not?

-- Scott