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.įor both URLs even if they should be different 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 The GCM will have to ask for new host specific credentials which willbe stored as Git Credentials Manager will only find that entry for URLs containing a user When you create an account in SourceTree it is created as a per user account, and indexed as such in Windows Vault. You should be able to delete that in SourceTree Authentication Tab.
#Completely remove sourcetree windows 7 password#
The bug I mentioned above only applies to Saved Password entriesįrom what you describe I believe you have deleted the 'secret' associated with the account in SourceTree but not the accounts.json record. This lists all the 'git:' prefixed entries in Windows Vault where there isn't a matching SourceTree account record.įor 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
Information is stored in %localappdata%/Atlassian/SourceTree/accounts.json and Windows Vault.ĭeleting 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 These are for Bitbucket, Bitbucket Server and Github only and include Git/Hg information and REST information. SourceTree lists two types of accounts/credentials in the Authentication Tab, Accounts and Saved Passwords
0 kommentar(er)
