Closed Bug 1223590 Opened 9 years ago Closed 9 years ago

Unable to login to bugzilla via login to github (fresh bugzilla account)

Categories

(bugzilla.mozilla.org :: Extensions, defect)

Production
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: bgaskin, Assigned: dylan)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Linux; Android 5.0.2; 404SC Build/LRX22G) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.76 Mobile Safari/537.36

Steps to reproduce:

Tried to login to bugzilla, didn't have an existing account.
Chose to login via github.


Actual results:

I was promoted for user name and password and notified on screen that a new bugzilla account was being created. Then I was just returned to the login screen (still not logged on).


Expected results:

I should have been logged on or been given a prompt to create a bugzilla password.


Eventually I created my login without using github.
Assignee: general → nobody
Component: Bugzilla-General → Extensions: GitHubAuth
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
Assignee: nobody → dylan
This appears to be a regression caused by 2fa. 

Does logging in with github work now that the account is created?
Flags: needinfo?(bgaskin)
Looks like it may be related to a CSRF protection (cookie/state not matching)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Attached patch 1223590_1.patchSplinter Review
This was a silly bug. Basically we need to check for a code param or an email param in a GET request. We're just checking for a code one now, which breaks when someone has multiple github accounts.
Flags: needinfo?(bgaskin)
Attachment #8685712 - Flags: review?(dkl)
Attachment #8685712 - Attachment is patch: true
Attachment #8685712 - Attachment mime type: text/x-patch → text/plain
(In reply to Dylan William Hardison [:dylan] from comment #1)
> This appears to be a regression caused by 2fa. 
> 
> Does logging in with github work now that the account is created?

Yes, that works.  As you say, now that I have my bugzilla account created I can log in via github.
(In reply to Dylan William Hardison [:dylan] from comment #1)
> This appears to be a regression caused by 2fa. 
> 
> Does logging in with github work now that the account is created?

Yes, that works.  As you say, now that I have my bugzilla account created I can log in via github.
(In reply to Dylan William Hardison [:dylan] from comment #1)
> This appears to be a regression caused by 2fa. 
> 
> Does logging in with github work now that the account is created?

Yes, that works.  As you say, now that I have my bugzilla account created I can log in via github.
(In reply to Ben Gaskin from comment #6)
> (In reply to Dylan William Hardison [:dylan] from comment #1)
> > This appears to be a regression caused by 2fa. 
> > 
> > Does logging in with github work now that the account is created?
> 
> Yes, that works.  As you say, now that I have my bugzilla account created I
> can log in via github.

Figured as much. Thanks for the bug report!
Comment on attachment 8685712 [details] [diff] [review]
1223590_1.patch

Review of attachment 8685712 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good. r=dkl
Attachment #8685712 - Flags: review?(dkl) → review+
To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git
   2c3a839..090abc7  master -> master
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED

I still face this issue.

Component: Extensions: GitHubAuth → Extensions
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: