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
This is the bug report for Anaconda cloud run on Ory. When setting up the 2-factor auth with Google Authentificator, correctly connects in the Google app, but every correct 6-digit number marks as incorrect, then redirects to error tab. See 'reproducing the bug' for more info.
Reproducing the bug
Steps to reproduce the bug:
From Anaconda navigator, select Create an account.
Proceed with creating an account in browser (I logged in via github).
In profile settings, set the password.
Enable 2-step verification and scan the QR with Google Authentificator.
Input the auth code in relevant field, should output as incorrect despite being correct 1-2 times; then opens the error tab.
Relevant log output
{
"id": "2ade001c-db07-4c8d-83ca-916cc22f793b",
"error": {
"code": 500,
"message": "An internal server error occurred, please contact the system administrator",
"reason": "Could not find they TOTP key in the internal context. This is a code bug and should be reported to https://github.com/ory/kratos/.",
"status": "Internal Server Error"
},
"created_at": "2024-04-02T16:07:38.494792Z",
"updated_at": "2024-04-02T16:07:38.494792Z"
}
Relevant configuration
No response
Version
On which operating system are you observing this issue?
macOS
In which environment are you deploying?
None
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Preflight checklist
Ory Network Project
No response
Describe the bug
This is the bug report for Anaconda cloud run on Ory. When setting up the 2-factor auth with Google Authentificator, correctly connects in the Google app, but every correct 6-digit number marks as incorrect, then redirects to error tab. See 'reproducing the bug' for more info.
Reproducing the bug
Steps to reproduce the bug:
Relevant log output
Relevant configuration
No response
Version
On which operating system are you observing this issue?
macOS
In which environment are you deploying?
None
Additional Context
No response
The text was updated successfully, but these errors were encountered: