Reopened: Re: SessionNotFound

[Cantor, Scott]

I guess a caveat since you mentioned something about waiting an hour...the reverse indexing from the SP/NameID back to the IdPSession(s) to which it's been associated for logout is a separate stored record that has an expiration based on what you set your session policies to.

Those records have an expiration that's based on how long you expect a given SP session to be around plus the sessionSlop value. So a failure to find a session in a totally separate browser would probably indicate that the logout attempt is happening after the reverse-index record had expired, meaning maybe you've got some values set too low.

The reverse indexing is just a record containing the list of all the IdPSessions involved, and its expiration slides forward any time the list gets updated:

Math.max(sessionList.getExpiration(), 
                                         spSession.getExpirationInstant() + sessionSlop)

(i.e. set expiration to the longer of "current" and "the new SPSession's expiration + slop value")

-- Scott