The Apple Keychain actually requires a username to be known in advance for the password lookup to work; if you don't include a username in your URL then SourceTree remembers the last username that was used to successfully log in to a given host and tries that one by default to look up the keychain entry. This can, however, be unreliable if you don't use the same username all the time on a given host. To make it unambiguous, include the username in the URL, like this:
Thanks. It worked. This is the correct anwser. No need to run pull on the terminal. In my case is simple as editing the repo URL and include my user as you mention, BEFORE the host. After that I restarted SourceTree and problem solved. The same applies for each new repo. Thanks! :)
Hi everyone, this is Ana from the Community Support team!
We’re seeing several recent responses saying that the solutions provided here do not work. This post originated in 2012, so whatever was valid at that time doesn’t necessarily need to be valid now. There could also be different reasons why Sourcetree is asking you for credentials, so there isn’t really a unique answer.
To make sure we’re helping everyone, I’ll be closing this thread now. If you encounter this issue now and the solution provided here doesn’t help you, please submit a new question and make sure to add the following:
Thanks and see you around :)
I tried but no success, but then I figure out:
- SourceTree use Embedded Git service
- Terminal use System Git, which I install via XCode
So, I just need to update SourceTree config via "Preferences -> Git tab -> Git Version" by select "Use System Git", then everything works well
Don't forget run steps as @Owen Peng suggest above. good luck
This has been bugging me for ages. I have an answer that now works for me on SourceTree V2.6 (123).
First go to keychain and remove any bitbucket entries (you may not have to do this but it helped me to work out that sourcetree had actually entered something)
Under sourcetree->preferences go to Accounts
Change Auth type to "OAuth" from Basic
Click on "connect account"
login to the bitbucket page from the pop-up window
Make sure protocol is 'HTTPS'
Bring up one of your git repos and pull it from bitbucket.
The first time it will ask if it can access keychain. Hit 'Always Allow'
You should then have pulled the repo.
Check in Keychain access to see if there is a new entry called 'Bitbucket Credentials'
If you have this then sourcetree should not ask you for your bitbucket password in future.
Time will tell if this keeps working. Good luck.
OH SWEET JESUS! After searching about this problem for over an hour and trying several different fixes, this is the one that FINALLY WORKED for me.
I had previously set-up two-factor authentication for Bitbucket and tried using an 'App Password', but that was not good enough. I couldn't make the repeated auth requests stop until I switched from 'Basic' authentication to 'OAuth', as Darren suggested.
I am running SourceTree 2.6.2 on Mac OS Sierra 10.12.6
Crazy that this is still an issue after so many years, but I ran into this today. The fix was to install git on the computer and use that instead of the embedded version. After a git pull and entering the credentials there I can now work in SourceTree without it asking for password all the time.
This is driving me MAD. Every once in a while, typically after some obscure update, SourceTree on MacOS starts to require my password on any push or pull action. Sometimes it works for months, then suddenly, I have to type in my password again. This is so strange. What is causing this, and why can't they fix this once and for all?! I am really considering to switch to GitKraken now.
We are seeing this eaxct problem for two accounts on our Team and it seems Atlassian have no clue what is going on, since they choose not to offer an answer to this crippling bug.
We have tried all the suggested 'fixes' but none have worked.
A source control system that you cannot access is not only completely worthless it is also endangering projects.
Atlassian how about you actually address this matter, since by your own account you are now comitted to provide support via the community.
For me, setting the Git client to "System Git" has solved the problem for now. But I have no clue why this has to be done once in a while. And until then, I already have forgotten that this setting is available. It's a shame that remembering the password does not just work out-of-the-box. This is such an essential feature, especially if you're using long, cryptical passwords, as I do. Always having to open your password manager is pretty annoying.
Setting Sourcetree to use System Git worked for me as well.
If I HAD to guess, I would imagine this error is permissions-based. If the copy of Sourcetree tries to read the keychain value for bitbucket, and can't, then it needs to continually ask.
When changing to System Git, since it's apart of the user's path, I think it actually triggers the system to display the dialog box asking for permission.
Again, at any rate, using System Git and running `git pull` worked for me.
I was running into the same issue and then realized that my SSH agent did not have my SSH keys loaded. So make sure that you have your SSH key loaded if that's how you are talking to your git repo server.
See here for more details of how to check you agent and see which keys are loaded: https://confluence.atlassian.com/bitbucket/set-up-ssh-for-git-728138079.html
Also see this if you discover that your keys are not loaded at startup/login on macOS Sierra:
Hope that helps
Remove all other authentications section in sourcetree other than git hub.
Then click Add or either go to Hosted repositories(to quickly check if it was successful) and click on edit accounts.
In credentials select OAuth and select refresh token. You will be redirected to bitbucket website and click on Grant access.
Now goto your fresh account in sourcetree and select Set as Default.
Done. Now you should see all your repositories in hosted repositories. It shows login error if it is not successful
This is still happening. Strangley it seems that if there are many differences SourceTree flakes out and tries to authenticate. You should be able to duplicate this by say coping a version of a project that has CR/LF windows style line endings but the repository has Linux style line endings. Removing the windows style line endings stopped SourceTree from trying to authenticate.
Sourcetree keeps asking me for login and password when pulling from external git or mercurial repository. I've tried different things:
- removing keychain entry: no result
- reinstalling sourcetree: helps, but the bug re-introduces itself soon and then until next reinstall it is still there.
During single pull it asks for password always two times. Adding user name to connection stirng helps in the form, that it remembers user name but still asks for password.
I had the similar problem. Every fetch/pull/push action requires password from my github account. I found the answer for this problem here
It helped :)
Using ssh connection but always prompted for a password. If I enter the password several times push does work but the password is never saved.
For me the solution was a bit more obscure.
By default ssh will always check for ~/.ssh/id_rsa and attempt to use that for any connection. In my case that id is not relevant for git, but is used for ssh to a different server.
The solution is to add a an entry in ~/.ssh/config which tells ssh to only use password.
Add the following lines:
Came across this same issue and multiple posts too. So consolidated my research and fix at one place https://stackoverflow.com/a/52884626/5107365. Summary is, problem solved when I used the same password for Atlassian's account address(which is the Gmail ID I used to OAuth to my bitbucket user), as that of my Gmail ID.
I too faced the same issue and got resolved.
Please follow below steps to resolve.
Source Tree -> Tools -> Options -> Updates -> Click on 22.214.171.1243 for update
Source Tree -> Tools -> Options -> Git -> GitVersion -> Click on Embedded and Update Embedded buttons.
Restart source tree and it works fine.
Hi folks, While the full post is over on our blog I'd like to share the dark theme we've got planned for 2019 here directly as well to keep the discussion going. The ...
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