Bitbucket account converted to Atlassian ID, can no longer access git repos in Sourcetree
Asked by Wesley Fok:

We have both a Jira/Confluence Cloud account as well as a Bitbucket team account. I used to have an Atlassian ID for the former (logging in via Google SSO and synced to our Google Suite) and for Bitbucket I had a standalone username/password login. We're moving to a different Google Suite instance, and on the suggestion of Atlassian Support, we disconnected our GSuite migration from Jira and Confluence. I then manually reactivated my user via a different admin user, and set a new Atlassian password. This has had the unintended side effect of linking my formerly standalone Bitbucket account to my Atlassian ID. As a result, I can no longer access any of my Git repositories in Sourcetree for Windows 3.1.3.

I've tried everything I can think of--creating a new Remote Account, using the generic Remote Account and adding Bitbucket credentials manually. I've used my old Bitbucket username and password as well as my Atlassian ID email address and new password, as well as a number of Bitbucket app passwords, in multiple permutations. The response is always the same: either I get a "Bitbucket Login" window with my username pre-set, for which no login/password combo works; or I just get error messages in the log window showing repeated "Invalid username or password" errors.

I even tried removing all Sourcetree configuration files from my system, renaming my old repository, and trying to clone the repository again with a fresh install of Sourcetree. Sourcetree can see my Remote Account still (somehow), and it shows a full list of my repos. But when it tests the repository URL to make sure it's valid, I get the same Bitbucket Login window that never works for me.

If I try to do these operations via the git command line, everything works fine as long as I use my Atlassian ID credentials instead of my old Bitbucket ones, so I know my login works. I also have access to all three services and have been able to validate OAuth in Sourcetree multiple times. But when it comes to actually DOING anything in Sourcetree, I'm completely out of luck. Please help.


Answers:
author: Stephen Sifers
body: Hello Wesley,

Thank you for taking the time to create a detailed review of the issue you're having after adjusting your login credentials for the Atlassian suite. Since you've already confirmed that using git via the cmd line works without issue then this is most likely an issue with your old credentials being stored. While you have cleared out the cache and re-installed this does not always remove the registry entry for the credentials itself. Please attempt the following to see if it clears your credentials:

1. Within Sourcetree, Navigate to Tools \> Options \> Git.
   1. ![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/60084i36272DFB8330DF7A/image-dimensions/183x103?v=v2 "image.png")
2. Within Git, scroll to the bottom under Git Version and Select Update Embedded.
   1. ![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/60085iB487F463594D614F/image-dimensions/223x197?v=v2 "image.png")
3. Approve the action and wait for it to complete.
4. Once completed, close out Sourcetree.
5. Once fully closed, open Sourcetree.
6. Retest to see if you're prompted for your credentials.

Please let us know if the above helps to resolve the issue.

Regards,  
Stephen Sifers

comments: author: Wesley Fok
body: I performed these steps, along with modifying the Git URLs to remove my Bitbucket username, and I did in fact get a login prompt (not Bitbucket/Atlassian-branded) that accepted my email address and new Atlassian password just fine. Thank you very much!


author: Stephen Sifers
body: Hello Wesley,

Very glad to hear you're able to get authenticated again within Sourcetree.

Regards,  
Stephen Sifers


Tags: cloud

confluence-cloud