-
Notifications
You must be signed in to change notification settings - Fork 6
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 get login flow
when going back in the browser history
#279
Comments
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/IAM-1051.
|
I am unable to reproduce this issue for some time now, can you verify that it's still happening and provide more precise instructions? |
https://iam.dev.canonical.com/stg-identity-jaas-dev-grafana-k8s/login~ happening here still |
This error happens on chromium, can't reproduce it on firefox. Looks like on chromium the back does not trigger the browser to fetch the page again, this results in trying to re-use the existing flow. Whereas on firefox I think that a new flow is created. |
Anything we can do for chromium? |
This is due to bfcache. It can be disabled with a header |
If you log in with email and password, login ui redirects to complete the 2fa. If instead of providing it you go back in the browser and attempt to sign in again, a
Failed to get login flow
error will be displayed:In login ui logs:
The solution is to 1) clear the browser cookies or 2) go again to the original url which will redirect to insert the password again (the email is cached).
The text was updated successfully, but these errors were encountered: