Closed Bug 1477169 Opened 8 years ago Closed 7 years ago

Navigation to Login screen after Auto Github Login fails

Categories

(Participation Infrastructure :: Phonebook, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aiyankovil, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce: Clicked Login Via Github and asked for two factor Auth,Since i have not enabled it Navigation back to login screen to login with mail id was not loaded instead redirected to home page If we are clicking login event again , it will navigate to the Github login , not to login page Actual results: Actual Results: Navigation to Home Page and on login click , directly to the Github Auth Expected results: expected Results: Navigation to Login Page with all the option
Sorry , the bug is for Mozillians.org website.Please consider this bug in Mozillians.org
Component: Phonebook → Account Help
Component: Account Help → Phonebook
Hi Hidde, can you please take a look at this?
Flags: needinfo?(hidde)
When you clicked login for the second time, did you see the login screen before you were sent to the GitHub Authentication page?
Flags: needinfo?(hidde)
@Kuruvilla George ^^
Default login screen is not loaded.. It's navigating to Github login My requirement was to login through Gmail, since I clicked Github at first I was not able to navigate to Gmail login in anyway.
Flags: needinfo?(hidde)
Hello Kuravilla George, This issue should now be fixed; we've updated the login page to only autologin when it hasn't happened in the previous ten minutes. We also disable autologin when the browser back button was used. With that, you can now get a fresh login screen by refreshing the login page or using the browser back button. Hope this helps!
Flags: needinfo?(hidde)
Thanks @hidde for the fix. @syamkumar @henrik thanks for the support.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.