-
Notifications
You must be signed in to change notification settings - Fork 977
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
Could not find the TOTP key in the internal context #2401
Comments
If I log out and log in again, it starts working again, meaning I can activate TOTP verification again. |
Thank you for the report, can you try doing the same flow you described, but loading a fresh settings flow - so calling the settings ui and removing the This is still a bug though of course, I just want to see if that's the problem. |
Yes, I was just about to try actually, will get back to you! :) |
Hi @aeneasr . Your suggestion solves the issue. Actually, I experienced a "related" problem, which was solved using the same method. If you'd like to, I can report this separately as well.
|
Thank you! I think they have the same underlying problem so it's ok to keep track of it here :) |
Great, thanks for responding so swiftly! :) |
Preflight checklist
Describe the bug
In a browser client using Ory Kratos: After activating 2FA with TOTP by scanning the QR code retrieved from after initializing the settings flow and successfully inputting the verify code generated by the paired Authenticator app, then disabling and then going through activation a second time, during the same privileged session, the following error is thrown:
Reproducing the bug
I was able to reproduce both in my own browser client as well as in https://kratos-reference-ui-react-nextjs.vercel.app/
Relevant log output
Relevant configuration
Version
v0.9.0-alpha.3
On which operating system are you observing this issue?
macOS
In which environment are you deploying?
No response
Additional Context
https://github.com/ory/kratos-selfservice-ui-react-nextjs
The text was updated successfully, but these errors were encountered: