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
Clean OAuth2 token #397
Comments
I've tried
and I've this in the console
|
I'm no expert at this and haven't used forgetClient(), but I use these as some sites drop a cookie (you can print out the cookies to check whether it's this):
btw. You can lookup error codes like -25300 at https://osstatus.com/search/results?platform=all&framework=all&search=-25300 |
Thanks for your answer, but cleaning cookie before runoauth does not seem to fix the issue, I will continue to dig EDIT:
It seems that some infos are stored somewhere but I don't know where EDIT2:
|
I've found attributes |
I'm not sure about the attributes you just listed (I do override Be sure to let us know what you learn. |
Ok I've opened the keychain-2-debug.db removed the entries in genp table with a name contain our app id and logoff again and I'm still reconnected immediately. I will double check if this issue truely come from swift app and not from server side, what I'm sure is that the revoking of access_token works (the DB is correctly updated) |
I've solved this issue, I just had to clean cookies for the SFSafariViewController (I've done that in PHP) |
Hello,
In swift I'm calling successfully a callback URL which revoke a token after the user is logout, and right after I call this to enable re-logging
But it re-log the user automatically when loading logging page (I see briefly safariVC but it is dismissed almost instantly), strangely the first logoff works well but if I relog I cannot sign off anymore and I have that line in the console when it relog
[Debug] OAuth2: Did exchange code for access [true] and refresh [true] tokens
In DB the previous token is deleted at the revocation and a new one is created, so I don't know how the user can be relogged without crendentials asked
The text was updated successfully, but these errors were encountered: