Starting today, I cannot connect to GitHub with my configured OAuth connection. Every time I try to pull or push it endlessly prompts me for my GitHub credentials, which I supply, but it rejects. My GitHub account is configured for 2 Factor Authentication (2FA) and it never prompts me for the 2nd code send to my phone, and no code is actually sent to my phone anyway.
All of this should be moot, however, because I am using OAuth and 'SourceTreeForWindows' is set up as an 'Authorized OAuth App' in GitHub.
Things I've Tried:
What gives? How did it just stop working all of the sudden?
I was able to fix it by ditching OAuth.
I removed the OAuth account under Options -> Authentication in SourceTree, then I generated a Personal Access Token in GitHub (under Developer Settings). Then I added a new GitHub account in SourceTree and selected "Basic" authentication instead of "OAuth" and used the Personal Access Token I previously generated as my password.
That got me all up and running again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Worked great for me, thanks! I enabled 2FA in Github, and somehow I messed things up, this post resolved it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This does not work with the latest Sourcetree 2.4.8.0
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Git just recently deployed a change that disables support for deprecated legacy TLS and SSH algorithms, including those that were used in older versions of some Git clients:
https://githubengineering.com/crypto-removal-notice/
Anyone found solution for this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was able to get the SourceTree 2FA dialog to pop up after uninstalling and reinstalling SourceTree a few times, upgrading system Git and rebooting a few times. Not sure which action fixed the problem of 2FA not displaying but there's a fix in that combination somewhere.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.