I recently applied a SourceTree update. I then spent the next 90 minutes or so trying to get Atlassian Authentication working so that I could once again push my commits.
This problem seems to return whenever there is an update to SourceTree.
I tried many different approaches, including upgrading by BitBucket Account to an Atlassian Account; and reinstalling SourceTree.
The problem varies in frequency; but returns whenever the SourceTree desktop client is left running. Simply logging in again causes the problem to go away for a little while. I think it returns after one performs a Commit.
Has Atlassian made progress in understanding the cause of these frequently reported Authentication problems?
Assuming you are using Sourcetree for Windows and Git then authentication is dependent on the Git Credential Manager for Windows, GCMW. Unfortunately there have been a series of bugs in this over the last couple of months. The latest release GCMW 1.18.3 seems to be much better and is bundled with Git 2.19.2 upgrading to that version of Git and switch Sourcetree to use in Tools/Options/Git as a System install is worth doing.
Additionally older versions of GCMW do not support TLS 1.2 so it is possible you are being effected by this, please see https://community.atlassian.com/t5/Sourcetree-questions/Unable-to-authenticate-on-Windows-using-username-password/qaq-p/954836#M26404 for more information
Hello Sourcetree users!!! With the recent removal of Bitbucket Cloud account passwords for app passwords (please see our Bitbucket Cloud community post for details on why we made this change for se...
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