-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
authentication fails with two factor auth #412
Comments
I use FreeBSD - thanks! |
Then you can download the source code and run |
Hey :) I did upgrade using the brew command. Just wanted to point it out. |
@picsoung Did you expect to get the code using SMS? Are you not using a mobile app such as Google Authenticator? Not getting the SMS is probably a bug with GitHub's API. Can you retry it a couple of times and see if you stil don't get the SMS message? |
I tried several times yesterday... and I did not get any text. I have a crappy old phone so it goes through SMS and not an app. |
@picsoung OK, I want you to try something that will help us see the requests being made. If you have a debugging HTTP proxy, then you can use it, but if you don't you can download mine. Simply put the # in one terminal tab
$ proxy 8888
# in another terminal tab
$ https_proxy=localhost:8888 hub ... Now all API requests will be routed through the debugging proxy and you should see the information in the proxy tab. That's the same method I use for debugging HTTP requests. Paste us the output, but remember to anonymize the encoded value in the |
Here is what I got
|
@picsoung Thanks for trying this. I just realized I was stupid and in my proxy script I stripped the |
No worries ;)
|
@picsoung OK, thanks to that I've found a bug in GitHub's API. I don't know when we can get it fixed, but until then you're stuck. You can try create a token manually from the site https://github.com/settings/tokens/new and save it in
|
yeah bug found ! 👍 thanks for your help :) |
hub initially tries to fetch user's existing OAuth token for hub if it exists, and will prompt the user for a 2FA code. However those who receive it via SMS would never get the code since a GET to GitHub's Authorizations API purposely doesn't trigger an SMS. There's some discussion as to whether this is an API bug for not, but in the meantime, make a dummy POST request for the sole reason of triggering the SMS. Fixes #412, closes #435, closes #445
hub initially tries to fetch user's existing OAuth token for hub if it exists, and will prompt the user for a 2FA code. However those who receive it via SMS would never get the code since a GET to GitHub's Authorizations API purposely doesn't trigger an SMS. There's some discussion as to whether this is an API bug for not, but in the meantime, make a dummy POST request for the sole reason of triggering the SMS. Fixes #412, closes #435, closes #445
If github two-factor auth is enabled then hub fails to ask for the second factor, and then fails to authorize.
The text was updated successfully, but these errors were encountered: