Bug: cloning via HTTPS broken after Atlassian account transition

Cloning with HTTPS is broken after the Atlassian account migration.

The clone path is "git clone https://veksler@bitbucket.org/feeorg/fee-cms.git"

"veksler" is my Bitbucket username.  This username does not work after migrating my Bitbucket account to my Atlassian account.  When I clone with SourceTree I get a credential error, and the username is read only, so I can't use my Atlassian credentials.

The workaround is to remove the username from the clone path in the Repository Settings.  This is annoying because I have more than 10 repositories in my SourceTree.  However SourceTree is still asking me for the old Bitbucket account - it must have the old credentials hidden somewhere.

login.png

1 answer

0 vote

Hi David

You should be able to authenticate using your Bitbucket username and your Atlassian account password. Does that work?

Alastair

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Jun 12, 2018 in Bitbucket

Do you use any Atlassian products for your personal projects?

After spinning my wheels trying to get organized enough to write a book for National Novel Writing Month (NaNoWriMo) I took my affinity for Atlassian products from my work life and decided to tr...

22,851 views 26 12
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you