CODEWITHSUNDEEP
gitbitbucketatlassian-sourcetreegit-credential-manager
DGRFDSGN
DGRFDSGN

Reputation: 675

Atlassian Bitbucket Sourcetree Git Credential Manager prompt

Atlassian Bitbucket Sourcetree Git Credential Manager keeps prompting me to authenticate.

I have tried several fixes, including the obvious:

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.

Upvotes: 16

Views: 45709

Answers (7)

jolyont
jolyont

Reputation: 1

I've just hit this problem. Windows 11. Sourcetree 3.4.17. I got the following CredentialHelperSelector pop up. It offered these options:

  1. no helper
  2. wincred
  3. wincred
  4. manager

option 4 didn't work. option 3 did. happy days. no idea why. CredentialHelperSelector options

Upvotes: 0

Akash Agrawal
Akash Agrawal

Reputation: 1

After trying a lot of things like - updated source tree, applied authentication multiple times, even close and open source tree, to fix the issue, what eventually worked was to select manager-core when it was asking for credentialhelperSelector.

Upvotes: 0

Willow
Willow

Reputation: 59

I did the same thing as 2 posts above (open powershell, edit ...), except that for credential helper I put manager-core instead of manager.

With manager I got error : "git: 'credential-manager' is not a git command. See 'git --help'."

Upvotes: 1

kalleguld
kalleguld

Reputation: 460

I Had the same problem starting on a fresh Win10 VM. Installing Sourcetree 3.4.11 and cloning a repository on Azure DevOps gave me a window called CredentialHelperSelector, as OP describes.

The solution for me was to install Git for Windows separately from https://git-scm.com/download and then telling Sourcetree to use that version instead of the one embedded in Sourcetree.

After installing Git For Windows, go to Sourcetree => Tools => Options => Git => Git version => [click "System"]

Upvotes: 4

prossel
prossel

Reputation: 161

Using SourceTree 3.4.8 installed on a clean Windows 11 in a virtual machine, I get the credential helper selection dialog.

I found out that selecting "manager-core" from the list and checking always use was the solution. If the popup comes again, selecting the second option "manager-core" was definitive. I don't know why there are several options with the same name, but the second one was the solution.

Also since I was cloning a repository (with https) from bitbucket, I also had to connect to my account in Tools > Options > Authentication > Add > select HTTPS and OAuth, Refresh OAuth Token.

Upvotes: 7

Neo
Neo

Reputation: 3584

Here is a fix:

From Powershell/Git Bash/Terminal from Source Tree, navigate to

%localappdata%\Atlassian\SourceTree\git_local\mingw32\bin\

or

C:\Users<User Name>\AppData\Local\Atlassian\SourceTree\git_local\mingw32\bin

#run

./git.exe config --edit --system

#opens config in VI editor

#update [credential] helper

[credential] helper = manager

Esc

:wq

Upvotes: 1

DGRFDSGN
DGRFDSGN

Reputation: 675

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

Upvotes: 11

Related Questions