shibboleth-dev - RE: [Shib-Dev] sessionid, previous session, assertions - web gardens, web farms, concurrent sessionstate locking....
Subject: Shibboleth Developers
List archive
RE: [Shib-Dev] sessionid, previous session, assertions - web gardens, web farms, concurrent sessionstate locking....
Chronological Thread
- From: "Scott Cantor" <>
- To: <>
- Subject: RE: [Shib-Dev] sessionid, previous session, assertions - web gardens, web farms, concurrent sessionstate locking....
- Date: Sun, 10 May 2009 15:57:30 -0400
- Organization: The Ohio State University
Peter Williams wrote on 2009-05-09:
> Ill read the spec/errata more to see what it says about sessionid values
in
> followup assertions for the same sp-audience. Hopefuly there is only 1, so
> only 1 value need be kept around in the app session to have (later) the sp
> invoke slo on the right set of SPs, per nameid.
IdPs aren't obligated to make use of the feature, and are free to set the
session index to the same value as the assertion ID. So, no, you cannot
assume that. The session index is a tool for the IdP only, to allow targeted
logout based on its perspective.
-- Scott
- RE: [Shib-Dev] sessionid, previous session, assertions - web gardens, web farms, concurrent sessionstate locking...., Peter Williams, 05/09/2009
- RE: [Shib-Dev] sessionid, previous session, assertions - web gardens, web farms, concurrent sessionstate locking...., Scott Cantor, 05/09/2009
- <Possible follow-up(s)>
- RE: [Shib-Dev] sessionid, previous session, assertions - web gardens, web farms, concurrent sessionstate locking...., Peter Williams, 05/09/2009
- RE: [Shib-Dev] sessionid, previous session, assertions - web gardens, web farms, concurrent sessionstate locking...., Scott Cantor, 05/10/2009
Archive powered by MHonArc 2.6.16.