IDP SLO endpoint confusion

[Wessel, Keith William]

Alright. So, unless I want to do some major hacking, no way to see what SP the user just logged out of to avoid displaying it in the list?

I suppose a half-hearted attempt would be to pull the hostname out of the referrer variable and lok for an entity ID in the list of those associated with the IDP session that also contains that hostname. That's a big assumption about the entityID, though.

Keith


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, June 06, 2013 5:04 PM
To: Shib Users
Subject: Re: IDP SLO endpoint confusion

On 6/6/13 5:21 PM, "Wessel, Keith William" <kwessel at illinois.edu> wrote:
>
>Now I'm thoroughly confused. I turned up protocol logging to debug and 
>confirmed that, yes, the ASLO extension was being sent from the SP. I 
>then saw that things were working the way they were supposed to this
>time: no logout page from the SP. I turned debugging back off, and 
>they're still working. So, whatever glitch was causing that I seem to 
>have inadvertently fixed. I wish I knew how, but whatever.

Whatever, at least there's no bug there.

>Now, we're back to null pointer exception caused by the presence of 
>this code in my logout.jsp:

There's no "loginContext" variable, it's not a login. I think now that I'm looking I was confusing my export of the session object into the Velocity templates with access to the message information. I don't see any readily obvious way to get at it. (It could be programmed to be possible, but I don't think I did so.)

-- Scott


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