-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
bug: invalid_grant when refreshing token #66
Comments
@Anotherjez what SDK version were you using? Is this the same issue you reported earlier? #65 shouldn't affect it, as the SDK will always request a new access token using the refresh token if no valid token is found in storage. |
The By default, the refresh_token has a TTL of 14 days, but you can modify this setting on your App details page. |
Not the same issue, using logto_dart_sdk 2.0.2.
But I always get the error when the sdk requests the new access token.
I don't think so. The refresh token should not expire daily. All my users had to sign in again everyday.
Yes, in my settings it is set to 14 days. |
Sorry for taking so long, MongoDB has announced the end of life of Realm Device Sync and for this project I was also using MongoDB for authentication along with Logto. Now that I only use Logto for authentication, it seems that the problem is solved. |
Describe the bug
The error occurs when a user's token expires and he tries to fetch the access token with the refresh token to get user data with
.getUserInfo()
function. This error only occurs with previously authenticated users and We are only using discord social connector for sign-in and sign-up. It seems that the error occurs with discord users who have 2FA.This error may be related to this bug.
Expected behavior
.getUserInfo()
working without errors.How to reproduce?
logtoClient.isAuthenticated
logtoClient.getUserInfo()
without errorsContext
This error has been happening since June.
Using the latest version of logto_dart_sdk.
Logto Cloud
Self-hosted, Logto version =
Screenshots
The text was updated successfully, but these errors were encountered: