Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Sourcetree connect to Github with 2FA does not work

I have followed all of the instructions.  The instructions say to copy and paste the password.  This doesn't even make sense since when you attempt to connect, SourceTree asks you to log in with a 2FA process and "supposedly" saves the OAUTH token, but nope.  It doesn't.

Creating a separate password pasting in the OAUTH token also does not work. 2FA makes SourceTree absolutely broken.  Is anyone working to make the documentation correct or make the application function properly?

1 answer

0 votes
minnsey Atlassian Team Apr 17, 2018


Can you confirm what version of Sourcetree and Git you are using?

In Sourcetree for Windows when you add/edit a GitHub account you have the option to use Basic Auth username/password or OAuth.

If you select OAuth you should be redirected to the browser to login, go through 2FA,, authorize and then be sent an access_token. This access token is then stored in the Windows Vault/Credential Manager for re-use by Sourcetree for REST interactions and by Git for its interactions.

Independently the Git Credential Manager for Windows, bundled with Git for Windows, supports GitHubs 2FA directly. Again it stores its credentials in Windows Credential Manager.

GitHub recently removed support for TLS 1.0 and 1.1 protocols this means you will need to update to Git 2.16 or higher to continue using http URLs for Git remotes.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Sourcetree

Tip from the team: configure your repos for hosting goodness!

Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...

3,270 views 4 5
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you