Sourcetree Removing KeyChain

[rinskip]

Good afternoon,

I have had a problem since updating to Mac OSX Mavericks 10.9.1 that when I try to Pull/Push/Fetch from a bitbucket Git repo it asks for my password. I enter my password and the operation is successful. A few moments later a prompt asks if I would like to give Source tree access to my keychain. At this stage a new entry is present in the keychain. I seleted Always Allow from the keychain access prompt and now the keychain entry is removed and the next time I request a push or pull I am required to provide my password.

From other questions I am using a http://<username>@bitbucket.... url, I have removed and readded the repo and also removed and readded source tree. I have tried to use KeyChain FirstAid and also Disk cleaner to check for inconsistent permission. Nothing yet has changed the problem.

Any advice?

[Deleted user]

This issue occured for me due to not having read permissions on all repositories that were bookmarked in SourceTree.

I fixed this issue by removing remotes from any repositories I no longer had access to. I then added my password back to the keychain and it has yet to ask me for my password again.

I'm guessing this could also be fixed by simply removing the bookmark in SourceTree.

[davidlormor]

Same issue here. Please implement a fix (been dealing with this for months!).

[powertux]

Version 1.9.8 (1.9.8) / OS X 10.10 b7

Also remove password credential from keychain.

[Tschoatscho Kettl]

...which is a real show stopper. If I allowed SourceTree access to my MacOS keychain I wouldn't expect that it will remove my Github credentials in any case (even if there's a reason from Atlassian's point of view). So please stop this: You should never use write access on my system keychain regarding anything else than your own domain. Github is not part of your domain.

[Kelvin Chung]

A domain of some sort, I suppose. eg. https://stash.mycompany.comor something.

I know that my GitHub key has this set, but my Stash keys do not.

[KieranA]

Hey there,

I've just fixed some issues with HTTPS URLs and the keychain in SourceTree, but they're relating to usernameless URL formats. This seems odd as we haven't changed anything yet, and from all the tests we've done we've not spotted anything unusual. There's not been any reports on jira.atlassian.comyet which is where us developers generally look, unfortunately we don't have much time for AAC as we'd like.

If you actually check the keychain can you see the precise URL that's being used as a remote in your repository?

Also, are there submodules that could be asking for an update which aren't in the keychain for some reason?

Cheers

[Kelvin Chung]

I'm experiencing the same problem where the keys to the Stash repository that I am working with suddenly disappear from my login keychain when prompted by git-credential-sourcetree for access. (Subsequently leading to password prompting due to missing keychain paths.) I basically had to re-establish the key by going into the repo settings and reconfiguring the remote to add the key back to the keychain. This would last until git-credential-sourcetree would ask for access again.

Upon inspecting the key in the keychain, I noticed that the "Where" attribute is blank. I haven't had a problem so far when I have added the remote URL's domain to the "Where" attribute by hand, so I suspect there is something amiss here.

[KieranA]

The credential helpers work by having 'get', 'store' and 'delete' calls to them. We recently (correctly) implemented all of the calls so that Git will call 'delete' and 'store'. SourceTree doesn't actually call these functions, it's Git that does it.

If auth fails then Git may call 'delete', removing the key from the keychain so that it can try again. This may be what's happening in your case. The username sticks around because SourceTree stores that against the remote URL.

What version of SourceTree are you using?

Cheers

[Kelvin Chung]

1.9.2 on OS X 10.9.3 here. So far I haven't seen any issues when the "Where" field in the key is filled in correctly; the key was created without the "Where" field set...

[KieranA]

I don't have any keys with the 'where' field is set. What are you expecting in there?

[Kelvin Chung]

A domain of some sort, I suppose. eg. https://stash.mycompany.comor something.

I know that my GitHub key has this set, but my Stash keys do not.

[Maurizio Margiotta]

Same problem here

[Brad Fol]

Also experiencing this issue, extremely frustrating.

OS X 10.9.2 with Sourcetree 1.8.1

[SK]

I am having this exact same issue. There is a point where the entries stay in keychain and SourceTree works without asking for passwords, but after some time the old saved entries are removed and the password is required once again. It seems like this occus when SourceTree wants to refresh the remote status after not having done so for a bit. I am on OSX 10.8.5. Can some one from Atlassian SourceTree comment on this issue?