Closed
Bug 1210826
Opened 9 years ago
Closed 9 years ago
Unable to complete 2FA enrollment on login.mozilla.com
Categories
(Websites :: login.mozilla.com, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Unassigned)
Details
1) Go to https://login.mozilla.com/enroll_google_authenticator
2) Click "Create Google Authenticator"
3) Scan barcode
4) Press "Finalise Google Authenticator"
Expected:
* The "test page" shown, where I can enter my google authenticator code to check it's working
* The MFA tab added to the menu navigation on login.mozilla.com
Actual:
* The test page shows for a split second, but then I get redirected to the page that shows me the various 2FA options (eg DuoPush vs Google auth vs yubi key) - that has a banner saying "Successfully Added 2nd Factor Auth Device". Its URL is https://login.mozilla.com/?added=true
* No MFA tab added to the site navigation sidebar
* Not prompted for 2FA when connecting via SSH jumphost
I guess this might have something to do with the "bypass 2FA" option that :soap set for me in the IRC scrollback in bug 1067914 comment 1. (I didn't need this option set per-se, I just wanted 2FA reset for my account, not disabled permanently).
If that is the cause, then please can you:
1) Fix the settings on my account
2) Display an appropriate error to the user, rather the redirecting to the start of the signup flow above.
Thanks :-)
Reporter | ||
Updated•9 years ago
|
Group: mozilla-employee-confidential
Reporter | ||
Updated•9 years ago
|
Summary: Unable to complete 2FA enrollment → Unable to complete 2FA enrollment on login.mozilla.com
Comment 1•9 years ago
|
||
You really shouldn't have ever been set to bypass, no one should.
The flow works as it should have, as you were set to bypass, duo automatically pushes you through.
I've set you back to being enforced.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•8 years ago
|
Component: General → login.mozilla.com
Product: Enterprise Information Security → Websites
You need to log in
before you can comment on or make changes to this bug.
Description
•