-
Notifications
You must be signed in to change notification settings - Fork 73
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
Unable to call revoke token and end session endpoints with signOut method #220
Comments
The problem with this is that you're not actually logged in. Yes, you have an access token, but you're not signed in. You can check if you're actually getting signed in in first place by logging something to the console on the callback url page. Unfortunately the demo inside this project also has the same problem. It looks like you're signed in, but you're not. |
I don't think this is the problem. I have debugged the method and I can get the access token and the refresh token. In fact if I don`t set revokeTokens to true the logout process works fine. The problem arises when I set revokeTokens to true. |
Sorry for replying back to you this late. I've tried to reproduce the issue and can't seem to reproduce it. I've managed to get the oauth flow working, but the logout process works fine for me even when i set revokeTokens to true. |
Yes, the flow works fine for me too, but when I debug the application I see that the revoke token endpoint is called but the end session endpoint is not. Can you check if this is happening to you? |
I can confirm that I have the same result. I never get redirected to the /endsession route (tested on ios). What you can try to do is the following: Where you call the logout method
and then you can replace the current route with for instance a login route. I'm using vue so for me it would be:
The final result would be something like this:
|
Hi,
I'm having problems calling the signOut method. I'm using this method with the revokeTokens argument set to true and I was expecting the application to call both the revoke token endpoint and the end session endpoint, but this is not happening.
As you can see in the following code, when revoketokens is set to true, revokeTokens() is called, then requestTokenRevoke(), and inside this method the TOKEN_RESPONSE_KEY is removed from memory. It then tries to remove the TOKEN_RESPONSE_KEY again, but since it doesn't exist, the application throws an error and stops.
This is the error message I get in Xcode:
The text was updated successfully, but these errors were encountered: