Issue with Automatic TOTP MFA Unenrollment Triggered by 'REVERT_SECOND_FACTOR_ADDITION' #8585
Unanswered
saipraneethTLS
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am working on a microservice, which is a Next.js-based application. I am encountering an issue where TOTP-based Multi-Factor Authentication (MFA) is successfully enabled for users in Firebase, but shortly afterward, it is automatically unenrolled. Initially, the TOTP MFA setup worked as expected, and I received an email notification confirming that MFA had been enabled for the account. However, immediately after the email is sent, a request is triggered in the logs labeled as
"REVERT_SECOND_FACTOR_ADDITION"
which removes the TOTP setup for the user.Upon reviewing the logs, I noticed that this request aligns precisely with the time the email is received, suggesting a possible connection between the email notification and the automatic unenrollment. Additionally, the logs indicate a
google.cloud.identitytoolkit.v1.ResetPassword
action is being triggered at the same time.I couldn't reproduce this issue, as I didn't face it in my private setup. Can anyone help me understand why this automatic unenrollment of MFA is occurring? Is there a specific Firebase configuration or security protocol that might be responsible for reverting the MFA setup? Could this behavior be tied to password resets or any other security mechanisms within Firebase or external sources?
Thank you in advance.
Log Details:
Beta Was this translation helpful? Give feedback.
All reactions