-
Notifications
You must be signed in to change notification settings - Fork 245
[Bug]: Google OAuth Token is not being refreshed #1088
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
Comments
I wonder if this is the same problem we're seeing in this report. Do you happen to get this error in the API logs when this occurs? if so, we may be experiencing the same thing. The front-end shows this, which seems to me to suggest, as you mention, that the refresh token isn't being utilized: |
Self-hosted All-In-One image, docker-compose. Same issue with non refreshed Google OAuth session observed. Log from api-service:
|
This happens when the refresh token is null and the accessToken expired, and the pod will gracefully shutdown and restart, also the refresh token will disappear and trigger this bug. |
- update activeauthtoken when first login - only update accesstoken and expirein when refreshing - check if refresh token is empty
After almost one day of testing I am not able to 100% confirm that fix is ok.
Not sure why token is empty? Maybe inactivity? |
I'm sorry, but this is still not working. I again updated to the latest Restarted docker, logged in after everything was up and running and worked on without any pause or inactivity. After one hour, I got this timestamps clearly shows that after one hour, RefreshToken was empty:
Is there anything else I could do to help debugging? |
Fixed and merged to dev, please check! |
This has been Fixed ( V2.6.0 ). So, closing out this Ticket. |
Is there an existing issue for this?
Current Behavior
The refresh token is not revalidated. My users are constantly being logged out.
Expected Behavior
Refresh the OAuth token.
Steps to reproduce
Set up the Google OAuth and use it for a while.
Environment
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: