SSO Session Cookies
Michael Grady
mgrady at unicon.net
Tue Feb 4 14:51:21 UTC 2025
One possible explanation for what you are seeing is that you did not "strictly do an upgrade", you changed some of the property values to the new values used in IdP 5. Including the idp.cookie.path = /. There are good reasons for that change related to security, but it did cause problems with some users' SSO session not seeming to be active/"honored".
The folks who had problems were running browsers that were caching the cookies from the IdP, and still had left over cookies from when the cookie path was /idp in IdP v4. And their browser was returning the wrong cookie to the IdP. Have any such users be sure to remove all cached cookies and try again.
If that isn't your problem, then no other ideas come immediately to mind.
> On Feb 4, 2025, at 6:47 AM, Cantor, Scott via users <users at shibboleth.net> wrote:
>
>> Can please someone have a look on this?
>
> "Somebody" is welcome to, but I am not in a position to debug your IdP for you. See list footer for why.
>
> You need to start with your logs. If it's reporting a failure to reuse a session or a login result, it's going to say something about that. If it's not seeing a session, then that's a different sort of issue.
>
> -- Scott
>
>
> --
> For Consortium Member technical support, see https://shibboleth.atlassian.net/wiki/x/ZYEpPw
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
--
Michael A. Grady
IAM Architect, Unicon, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20250204/6ca1ff14/attachment.htm>
More information about the users
mailing list