We are using Okta for our customer facing applications and not employees (yet). Customer login to each app on their own and do not have a ‘tiles’ landing page. Single-Sign-On kicks in as they go from application to application.
In case you want to logout of Okta (all of Okta, not necessarily each app), and send the user back to the original application where they clicked logout, I suggest this pattern:
https://{oktaOrgUrl}/login/signout?fromURI={redirected logout url}
A couple of notes here.
fromURI IS CASE SENSITIVE. I tried several combinations and they would all send the user back to the configured default app for sign-in widget and not the {redirected logout url}.
2.If using OpenId, I believe you need to ensure the {redirected logout url} in configured for Logout redirect URIs
I was testing your suggestion and confirmed that redirecting to the URL and not the ‘tiles’ landing page was working as of a week ago.
It is now currently redirecting to ‘tiles’ once a user logs out of the application.
Is this pattern still working properly on your application?
Not OOTB, no. Each application will be managing its own session, so while the /login/signout route can end a user’s session in Okta, it will not affect the sessions for any of the applications the user has logged into and these sessions would need to be terminated at each SP.
Thank you @kevintparker ! After a few hours of debugging, you saved me a couple more probably. Case sensitive, and don’t forget to add the url to the Security > API link section.