No active session(s) found matching LogoutRequest

[Nate Klingenstein]

Ike,

Here's basically what you need to know.  The secondary lookup for a session for user nmanda4 for that service failed.

> 2019-07-17 21:35:00,557 - 10.120.136.133 - DEBUG [net.shibboleth.idp.session.impl.StorageBackedSessionManager:834] - Performing secondary lookup on service ID https://xxx.xxx.xxx.xxx:14782/ and key nmanda4
> 2019-07-17 21:35:00,557 - 10.120.136.133 - DEBUG [net.shibboleth.idp.session.impl.StorageBackedSessionManager:856] - Secondary lookup failed on service ID https://xxx.xxx.xxx.xxx:14782/ and key nmanda4
> 2019-07-17 21:35:00,557 - 10.120.136.133 - INFO [net.shibboleth.idp.saml.saml2.profile.impl.ProcessLogoutRequest:402] - Profile Action ProcessLogoutRequest: No active session(s) found matching LogoutRequest

> Destination="https://xxx.xxx.xxx.com:14782/"
> Secondary lookup failed on service ID https://xxx.xxx.xxx.xxx:14782/ and key nmanda4

Assuming you sanitized the email and the.xxx actually matches the .com, then we're back to either my previous set of ideas or the application is sending back a NameID that doesn't match the one it received.  Either way, one or the other doesn't match, the required SessionStorage is not being used, or the idp.session.secondaryServiceIndex needs to be toggled to true.  I can't think of any other real explanation.  Maybe someone else on the list can.

Best,
Nate.