[EXTERNAL] Re: Logon is looping after apparent successful authentication.

Cantor, Scott cantor.2 at osu.edu
Fri Jun 1 19:50:10 EDT 2018


> 2018-06-01 19:24:09 INFO Shibboleth.SessionCache [3]: new session created: ID (_53ac1bab9c3efca559d3f5ff7b81dcce) IdP
> (https://devsaml.homedepot.com) Protocol(urn:oasis:names:tc:SAML:2.0:protocol) Address (130.211.3.197)

> 2018-06-01 19:24:09 INFO Shibboleth.SessionCache [1]: removed session
> (_53ac1bab9c3efca559d3f5ff7b81dcce)

That's deeply suspicious. It screams "IP address change" so native.log should explain why it's asking to invalidate the session it literally just created a millisecond before.

That isn't consistent with a cookie problem and the only thing it is consistent with is client addresses changing.

-- Scott



More information about the users mailing list