Routing Problems with SLO

Tue Oct 4 16:37:23 EDT 2016

Logging out of the broken Docker version takes me to: /idp/profile/Logout;jsessionid=502910252EEEAB7310CD165D57926C04?execution=e1s1

Logging out of the production one takes me to: /idp/profile/Logout?execution=e10s1&_eventId=propagate

What would be causing the logout event to not get recorded in the logs?

Where do I go to look at the session management? I've never had to directly debug cookies before, so any pointers on how to do this would be helpful.

Thanks for your help

    David Newswanger

________________________________
From: users <users-bounces at shibboleth.net> on behalf of Cantor, Scott <cantor.2 at osu.edu>
Sent: Monday, October 3, 2016 4:42:57 PM
To: Shib Users
Subject: RE: Routing Problems with SLO

> I'm working on migrating our IdP from Tomcat to a Jetty based Docker
> deployment. At the moment, everything works except for SLO. When a
> request is made to idp/profile/Logout, it appears as though
> logout_complete.vm is being rendered instead of logout_propagate.vm and
> so the user remains logged in. I don't see anything useful in the logs however
> I'll include them at the end of the email just in case.

Your logs are not showing any use of the logout feature.

-- Scott

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161004/590e37d2/attachment.html>