SAML: IDP initiated saml logout not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-12-2017 01:11 AM
Hi,
I configured my IDP (a trial PingOne instance) to initiate a SAML logout session (by navigating to
https:// sso.connect.pingidentity.com/sso/initslo )
This means Ping sends ServiceNow a LogoutRequest, and expects a LogoutResponse.
I tried configuring navpage.do as the SAML consumer, but this does not kill the session.
obviously /logout.do works but that just initiates the SAML logout again (and sends a LogoutRequest to Ping)...
I couldn't find any SSO scripts that handle a LogoutRequest from the IDP...
Any ideas?
thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-25-2017 12:01 PM
idangadot we have the same issue , did you resolve your issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-25-2017 12:05 PM
Unfortunately no,
We realized that (a) the SLO flow is too surprising for the user (imagine logging out in one app and getting logged out of all others),
And (b) — probably because of (a) — none of the other SaaS apps/IDPs we use fully support it anyway…
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-02-2017 04:25 AM
Similar issue here.
After proper SSO validation with our own IDP we can access ServiceNow. Later we trigger a logout from our application but the logout process is not triggered instead we are redirected to ServiceNow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2019 10:10 AM
We are having the exact same issue. Did you ever come up with a solution or workaround for this?
Most of our systems use ADFS, and when ServiceNow is the first Service Provider accessed, subsequent logout requests from other apps in the same browser session redirect to ServiceNow.
Currently we have a separate ADFS access policy configured to get around the issue, but this defeats the purpose of SSO...