Was *all* HTTP-based access deactivated?

Question

I had made the transition to key-based auth for my main project a while ago, then it stopped working about Feb.

The reason I ask, I had a variety of minor projects that were using HTTPS, they continued to work, so I assumed I had done something while learning the keys (like creating an expiry...)

But over time, all the HTTP repositories have failed, and when I went looking in the documentation, they provide instructions only for SSH keys.

Patrik S · Answer

Hello @Moby QT ,

The app passwords are linked to a user account, not to a specific repository. Since all the repos were affected I would suspect that some wrong credentials were cached in your local system which was causing the authentication to fail.

I would suggest trying to create a new app password and test cloning a repository over HTTP using the following syntax :

git clone https://USERNAME@bitbucket.org/WORKSPACE/REPOSITORY.git

You should be prompted to provide your app password. If that does not happen, it means the credentials are cached in your system (MacOS keychain or Windows Credential manager) and you will need to clear the cache to refresh the credentials and execute the git clone again.

Thank you, @Moby QT !
Patrik S

Moby QT · Answer

I've currently switched to SSH, for all the projects.

But I'm still somewhat confused about what happened.

I have several projects that were working, and when I look at the "App passwords", I see only one. But I had several repos, so were they using the older (website/UI) password?

When I look at audit log, I see several entries related to SSH and the app-password, but nothing related to the other repositories...

In "Sessions", I see two active sessions, and 6 inactive sessions, five of which were logged out on the same day -> 2022-11-23, and then the last on 2023-02-20.

Patrik S · Answer

Hello @Moby QT and thank you for reaching out to Atlassian Community!

Interacting using git with Bitbucket Cloud repositories is available using both HTTPS and SSH. Instructions on how to use HTTPS are outlined in our Clone a git repository documentation.

When using HTTPS, the remote-url when cloning the repository will look like the following :

git clone https://USERNAME@bitbucket.org/WORKSPACE/REPOSITORY.git

Where you will need to replace the USERNAME with your bitbucket account username (you can check it under your account's personal settings ), and the WORKSPACE and REPOSITORY with the corresponding names of the repository you want to clone.

When prompted to input your password, you will need to provide a valid App password created under your account - this is not the password you use to login in the UI. If you haven't created an app password yet, you can do so by following the steps in Create an app password article.

If you run into any issues following the instructions above, we kindly ask you to share the exact command you are executing and the error you are receiving so we can investigate further.

Thank you, @Moby QT !

Patrik S