Closed
Bug 1452397
Opened 8 years ago
Closed 8 years ago
Mozillian sign up using email issues error
Categories
(Participation Infrastructure :: Phonebook, defect)
Participation Infrastructure
Phonebook
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: chayadanz, Unassigned)
Details
Attachments
(1 file)
|
188.42 KB,
application/pdf
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Steps to reproduce:
-Navigate to Mozillians.org
-Click 'Log In/Sign Up'
-Enter email address for 'Log in with email or third-party'
-Click 'Enter' and then 'Send email'
-Navigate to email and click on red button 'SIGN IN TO MOZZILLIANS ORG'
-Error message displayed on main screen (see attachment Output4)
-Try again, this time clicking the alternate link provided in the email
-Link navigates to Mozillians.org home page
note: Google Chrome was used in this process
Actual results:
With option 1: Error message (see attachment 'Output4')
With option 2: Navigates to Mozillians.org home page (see attachment 'Output5')
Expected results:
I would assume clicking on either of the links provided in the email should navigate to some place that would allow me to continue the sign up process (I ended up logging in/signing up with GitHub).
Comment 1•8 years ago
|
||
Hi Chaya,
thanks for your bug report. This seems like a scenario that we designed for:
There is a hierarchy of "secure logins":
* Mozilla LDAP
* Github+2FA
* Google
* Passwordless email
Once you log in with a more secure authentication provider, we require you to use that in the future. That's why the error message tells you to use Github. We are continuously working on making our login screen "smarter". Hopefully it would tell you very soon that your most secure auth provider is Github instead of allowing you to enter a dead end.
Sorry for the bad experience.
Best regards,
Henrik
/cc @hidde
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•