Hi Antonis, James, P.
There is a bug in the current, 126.96.36.199 release when trying to delet some credentials from the 'Saved Passwords' list in Tools/Options/Authentication tab. There is a fix going through Beta testing at the moment.
You can work around this currently by deleting entries from the Windows Vault, using Win-Key typing windows credential manager and deleting the relevant entries that are prefixed by 'git:'
If it is a problem deleting from the 'Accounts' list then that sounds like a different/new issue.
SourceTree lists two types of accounts/credentials in the Authentication Tab, Accounts and Saved Passwords
These are for Bitbucket, Bitbucket Server and Github only and include Git/Hg information and REST information.
Information is stored in %localappdata%/Atlassian/SourceTree/accounts.json and Windows Vault.
Deleting entries from Windows Vault, just deletes the password or OAuth token used by Git/Hg/REST, but does not delete the Account record which holds information about whether to use HTTPS/SSH etc
This lists all the 'git:' prefixed entries in Windows Vault where there isn't a matching SourceTree account record.
For example if you use Git to manage a private repository from Visual Studio online, an entry will be createdin Windows Vault and will be lists by SourceTree under Saved Passwords
The bug I mentioned above only applies to Saved Password entries
From what you describe I believe you have deleted the 'secret' associated with the account in SourceTree but not the accounts.json record. You should be able to delete that in SourceTree Authentication Tab.
When you create an account in SourceTree it is created as a per user account, and indexed as such in Windows Vault.
The Git Credentials Manager will only find that entry for URLs containing a user
If you try to clone a urls such as
The GCM will have to ask for new host specific credentials which willbe stored as
So the 'make default' option will take a user specific set of credentials and copy then to a host specific entry, hence they will then re-appear in the Saved Passwords list
Its wrth being aware that this is a limitation of the Git Credentials Manager for Windows (GCM) it can only support a single set of credentials for a given host URLs that do not contina a username.
will store credentials under
for both URLs even if they should be different
If different credentials are required for team1 and for team2 the GCM cannot store both sets, so if you swithc between repos frequently the GCM will constantly be providing the wrong credentials to Git and having to re-prompt the user to enter the right credentials.
User specific URLs do not have this problem, because the credentials are stored per user.
will store credentials under
I'm having the same issue on SourceTree v188.8.131.52.
I had to change my password on GitHub, now SourceTree cant access it (no Pull or Push).
I tried deleting the passwords, deleting the cached authentication entries, editing them - but it all fails.
uninstalled and reinstalled SourceTree, dragged local repos into SourceTree - now I'm OK.
Sourcetree Version 184.108.40.206 (Feb 2018) Win 10 (latest build), 64bit
Still having massive issue with Authentication - Unable to delete any account that uses REST and having to resort to Windows Vault for manual deletion.
Completely unable to use GitHub personal tokens to work (https or ssh) - with or without 2FA turned on. Will not work on either of my Win 10 machines. (GitHub 2FA tokens working fine on my colleagues Mac's and I'm following the exact same process.)
I'm very familiar with 2FA, tokens, Oauth, and using public/private keys across a myriad of systems and OS's. So whilst I'm allowing for an element of pebcak, I suspect it's not all me.
So far have wasted 4 hours attempting to get 2FA to work with Github (mandated by my client)
(Basic authentication works fine)
Can you check that you are using a version of Git >= 2.16? GitHub removed TLS 1.1 and 1.1 support recently and the Git Credential Manager that ships with Git for Windows had to be updated to v1.14.0 to cope. This ships with Git 2.16 or higher
Embedded Git on one of my Win10 was 2.11
Using 'Update Embedded Git' button will only update it to PortableGit-220.127.116.11
The download path is;
My other win10 was already Embedded Git 2.15.1 and will not update any further.
My alternative is to use a system git - which last time I used a system Git with Sourcetree it caused me no end of grief and I had to uninstall everything and start again.
(Footnote: I know. Windows is a complete PIA to develop for)
Supported Platforms macOS Windows To make using Sourcetree as simple yet powerful as possible we embed (bundle) dependencies such as Git, Git LFS, and Mercurial. We strive to keep these...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs