Why did Atlassian break the Bitbucket <-> Sourcetree Integration and remove username auth?

[tufelkinder]

After having a basic username account for many years on Atlassian, I have been forced to switch to an email-based username. Except that this results in all https://user@bitbucket.org/repo URLs no longer functioning properly. And Sourcetree cannot check out or clone my repos.

I have changed my password and successfully authenticated with OAuth through Sourcetree, but still, it just keeps popping up an Atlassian login window every time I try to clone a repo and no combination of credentials allows me to log in and complete the authentication process and clone my repo.

Just let me use a username! What is the deal? Why do people have to keep breaking systems that are working?

[Mike Corsaro · Accepted solution]

There was an issue with the Git Credential Manager that is probably causing this. You can read more about it here

To fix it, you should be able to download v1.17.1 of the GCM here. Make sure you switch to "System Git" under Options > Git.