<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00007fqEB7SAMOkta Classic EngineSingle Sign-OnAnswered2024-04-15T12:42:56.000Z2020-01-31T14:42:28.000Z2020-02-05T16:53:57.000Z

98axd (98axd) asked a question.

Triggering Single Logout URL

When is the Single Logout URL triggered? I have an Okta developer account and a single application configured with SAML SSO. The login works fine. I have also entered a (publicly accessible) URL in Advanced Settings -> Single Logout URL along with the public cert for my test server.

I thought this meant that when logging out of Okta, a request would be sent to the SP Single Logout URL triggering a logout within my app. The endpoint exists and works fine but I never receive a request there when logging out of Okta. I'm not getting any errors, it's just that the URL is never contacted.

Am I misunderstanding Single Logout? I'm NOT trying to log users out of Okta after they log out of my app. I am trying to propagate logout to my app after a user logs out of Okta.


  • bc221 (bc221)

    SLO only works when it's SP initiated ( logout of app -> logout of Okta) as Okta doesn't have control over the app session lifetime but when the request is coming from the Service Provider, then we can log you out of Okta

     

    This is not possible - I am trying to propagate logout to my app after a user logs out of Okta.

    Expand Post
This question is closed.
Loading
Triggering Single Logout URL