You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the user clicks the logout button, the web app will trigger auth.signoutRedirect() and clear the session storage related to oidc:user. and will be redirected to the IDP logout page to show that the user has successfully signed out.
But, when the user tried to access the web again it seemed like it wasn't completely logged out. I noticed that the web still got the authorization code params automatically on the browser which then makes the user stay logged in.
Any idea why this happened? how to properly logoff the user completely from the app and IDP?
The text was updated successfully, but these errors were encountered:
@ValGab thank you for your response, I've updated the issue to add more context to my logout implementation and it seems I made a mistake when calling the clear session method.
I've tried your implementation, but still no luck.
I've configured a single logout with
auth.signoutRedirect()
with a logout button in the UI.Here is my configuration:
auth config
logout implementation:
When the user clicks the logout button, the web app will trigger
auth.signoutRedirect()
and clear the session storage related tooidc:user
. and will be redirected to the IDP logout page to show that the user has successfully signed out.But, when the user tried to access the web again it seemed like it wasn't completely logged out. I noticed that the web still got the authorization code params automatically on the browser which then makes the user stay logged in.
Any idea why this happened? how to properly logoff the user completely from the app and IDP?
The text was updated successfully, but these errors were encountered: