Issue 3098 in reviewboard: Cannot link a GitHub account with two-factor authentication enabled

2013-09-22 Thread reviewboard

Status: New
Owner: 
Labels: Type-Defect Priority-Medium

New issue 3098 by ch...@orr.me.uk: Cannot link a GitHub account with  
two-factor authentication enabled

http://code.google.com/p/reviewboard/issues/detail?id=3098

What version are you running?
1.7.14

What steps will reproduce the problem?
1. Attempt to add a GitHub repository with Link a new account
2. Enter the user/pass for a GitHub account with 2FA enabled

Error is shown:
Unable to link the account: Must specify two-factor authentication OTP  
code.



The documentation says that one option is to send the OTP code via an HTTP  
header:

http://developer.github.com/v3/auth/#working-with-two-factor-authentication

--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/groups/opt_out.


Re: Issue 3098 in reviewboard: Cannot link a GitHub account with two-factor authentication enabled

2013-09-22 Thread reviewboard

Updates:
Status: Confirmed
Labels: Milestone-Release1.7.x Component-HostingServices

Comment #1 on issue 3098 by chip...@gmail.com: Cannot link a GitHub account  
with two-factor authentication enabled

http://code.google.com/p/reviewboard/issues/detail?id=3098

We'll look into possibilities for implementing support for this. As it is  
today, we don't have a way to enable this. You *can* call their  
authorizations API yourself with the proper headers, using curl or  
something, and then create your own Hosting Service Account database entry  
with the resulting payload from that API, to get around this. That's  
clearly not a good long-term solution, but from their docs, it sounds like  
it would work.


--
You received this message because this project is configured to send all  
issue notifications to this address.

You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/groups/opt_out.