Identifying the SP initiating logout

Wessel, Keith William kwessel at illinois.edu
Wed May 29 16:38:17 EDT 2013


Thank you, gentlemen. This should work.

And thanks for the word of warning, scott. Yep, we understand that this is less than perfect, but it's better than nothing in an already imperfect world of federated logouts.

Keith


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, May 29, 2013 12:37 PM
To: Shib Users
Subject: Re: Identifying the SP initiating logout

On 5/29/13 1:30 PM, "Peter Schober" <peter.schober at univie.ac.at> wrote:

>* Peter Schober <peter.schober at univie.ac.at> [2013-05-29 19:28]:
>> * Wessel, Keith William <kwessel at illinois.edu> [2013-05-29 18:45]:
>> > For now, we'd like to exclude the SP that initiated the logout
>>request from that list. I'm thinking a simple if inside the for loop 
>>that displays the entity IDs, but I'm not sure how to obtain the 
>>entity ID of the SP to exclude.
>> > 
>> > Any help with where that info can be obtained from?
>> 
>> See "Relying Party Metadata" in
>> 
>>https://wiki.shibboleth.net/confluence/display/SHIB2/IdPAuthUserPassLo
>>gin
>>Page
>
>Actually all you need to get at the SP's entityID is in the example 
>above that,

Yeah, it should be the same for (SAML) logout.

But one should understand that the list of services here is going to be inaccurate for various reasons involving limitations of the session cache.
It should be viewed as best effort, but not gospel.

-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net


More information about the users mailing list