-
Notifications
You must be signed in to change notification settings - Fork 61
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
Failed to login, get "Oops, your session has expired. Please try again." #240
Comments
I suspect it's caused by the sync lag between the redis master and redis slaves. A few retries would solve this. |
@zhaohuabing you might want to have a look at an alternative implementation which is server side stateless, which means it can scale with the amount of replicas without a need for redis/db as a session store. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes failed to log in the first time, but succeeded after a refresh.
user navigates to url -> redirected to OIDC provider -> login -> redirected back to original service -> user sees "Oops, your session has expired. Please try again."
in the browser -> user can refresh the page which fixes the issue and user is signed in
log from this event:
The text was updated successfully, but these errors were encountered: