Atlassian Bitbucket Sourcetree Git Credential Manager keeps prompting me to authenticate.
I have tried several fixes, including the obvious:
Entering auth, prompt re-appeared in 15 sec.
Deleting all saved passwords. -Didnt work for me, prompt re-appeared in 2-3 min.
Updating Git Cred mngr - no effect
Updating Sourcetree - no effect
Reinstalling services - no effect
Deleting App data temp dir - no effect
Forcing password update - no effect, actually made it worse.
It keeps prompting me to log in with the wrong username over and over. I'm on Win10-64Bit, using Sourcetree V.3.0.6.
After reading this post on the Atlassian forum, I tried this:
Login with e-mail NOT username see this comment:
Bo Anderson Aug 06, 2017 • edited Jun 20, 2018 EDIT (20 June 2018): Recent changes to Bitbucket authentication has also meant that you must use your email (NOT your username) when logging in. Currently, logging in with your username is still accepted but seems to cause several issues ranging from this repeated login prompt issue to the "too many login attempts" error when pushing.
I've not seen the issue occur for non-Bitbucket accounts.
(29 Aug 2017): The embedded Git has now been updated, alongside the release of Sourcetree 2.1.11.0. After updating SourceTree, go to Tools > Options > Git and click "Update Embedded Git" to get the latest version (at least 2.14.1).
The majority of issues in Git Credential Manager for Windows have been fixed in recent versions. The latest version (1.12.0) released a couple days ago fixed the remaining issues I had with Bitbucket authentication.
The latest Git Credential Manager for Windows is included in the latest Git for Windows. Until Atlassian updates their embedded version, you could install Git for Windows 2.14.0 and within SourceTree, click "Use System Git" in Options.
Kris's solution also works if you only want to update Git Credential Manager for Windows specifically, though does require config changes.
This actually made it much worse, and I am prompted to login for every team member I'm teamed with.
Actually fixed this with the help of a colleague. He mentioned i should take a look in the Windows Network password credential manager go to settings -> search for password and open the Network password credential manager, in here i could easily remove the stored Git passwords, finally fixing this problem with bitbucket prompting me to reauth all the repo's, including the ones i didnt own. Jeej! Thanks Mitchel