-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser cookies are not cleared on logout() #624
Comments
Hi, are these the cookies for the federated IdP? |
Yes, correct. |
Hi @iuriirodyk, as mentioned in the article here - https://auth0.com/docs/authenticate/login/logout/log-users-out-of-idps It depends on the IdP and some might not implement this feature. The ones that are supported are called out in the article. Any chance you can share what IdP is failing for you here? |
That's none of the listed ones. I'm more after clearing the cookies on the app/browser side rather than trying to tweak IDP. But looks like it's not possible. Will probably close it as unresolvable |
Unfortunately, it looks like @iuriirodyk, you can provide product feedback here if you want and our PMs could explore more on this. I'll close this issue now. |
Describe the problem
Hi Community!
We’re using Auth0 sdk for Android version 2.6.0 and on logout we’re not able to clear cookies. We’re using federated auth and custom tenant if it matters.
Redirect URL on logout() doesn’t do anything either, federated parameter same. Scheme is the same custom scheme as for login. All works well, but cookies are still no matter what and the user doesn’t start from the very first login page upon next login in the app.
Chrome Custom Tab cookies are not visible for the Cookie Manager, so I’m guessing only Auth0 SDK can get it done.
What was the expected behavior?
Browser cookies are cleared after
WebAuthProvider.logout(auth)
and upon next login there are no cookies from previous users.Reproduction
There are just 2 methods that we use:
login()
andlogout()
.Environment
The text was updated successfully, but these errors were encountered: