You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Clearing browser cookies will force the re-authentication behavior to happen and thus avoid this issue, but this is really cumbersome to do every time the access token expires.
To Reproduce
Steps to reproduce the behavior:
Setup Google Oauth2
Login with Google Oauth sucessfully
Wait until access token expires in browser (should take a day or two?)
I added a new branch to my fork of Calibre-Web to help fix this issue. When you get the token expired message you would click on the "clear token" button on the login form. This will clear the session and token cookies. And it should work again.
Describe the bug/problem
If the user's Oauth2 access token has expired, instead of prompting for the Oauth2 login again, calibre-web just outputs a
error and refuses to login.
Clearing browser cookies will force the re-authentication behavior to happen and thus avoid this issue, but this is really cumbersome to do every time the access token expires.
To Reproduce
Steps to reproduce the behavior:
Logfile
Expected behavior
If the user access token has expired, login with Oauth should redirect to google again for re-authentication.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here. [e.g. access via reverse proxy, database background sync, special database location]
The text was updated successfully, but these errors were encountered: