What does end of support for passwords mean for me?

[rhouse2015]

I just got an email about end of support for passwords. I have one password which I use when doing git pull, push, and clone.  Will I no longer be able to do these git commands as I do now?  How will I do them?

Thank you,

Roger

[seanaty · Accepted solution]

For reference, here is a link to the announcement: https://developer.atlassian.com/cloud/bitbucket/deprecation-notice-password-authentication/

What this means is that Atlassian passwords will only let you interactively log into Bitbucket (e.g. via the Bitbucket.org website in a browser) as well as other Atlassian products.

If you'd like to use the API or Git over HTTPS you can still do so, you just need to create a new app password. It's really easy to do in the UI.

What this means is you'll have 2 (or more) passwords:

1. Your Atlassian password which signs you into all Atlassian products.

2. A Bitbucket-specific app password that lets you interact with the API or with Git.

N. You can create however many app passwords you want with differing levels of access (scope).

You can also uses SSH to push with Git as well.

Basically everything is the same as it was before, you just need to create a new password and start using that.

[rhouse2015]

Thank you.  Very helpful.

[Ruhan Coetzer]

I am pulling my hair out with this change! 

Your link doesn't work and the documentation hasn't been updated. 

I'm trying to push to my Bitbucket repo using VS code. I've installed the Atlassian extension, but the extension does not have a 'push' command, only clone and pull??! No wonder the rating for the extension is so poor.

I also tried using the Git extension for VS code, but this relies on password authentication.

Where can I find updated information on how to do a push request with password authentication being deprecated?

[Ruhan Coetzer]

I have also tried creating an app password to use with the Atlassian VS code extension. However, the extension asks for the repo URL. 

I provided the URL without the user name: https://bitbucket.org/coetzerr/natisbooking.git

However, when I enter the credentials for the app password, authentication fails

[Ruhan Coetzer]

The documentation is a mess. I finally got to the root cause. I managed to find this eventually.

Using an app password
An app password is a substitute password for the user account where you configure it, so you simply use it when authenticating with Bitbucket:

username: your normal Bitbucket username

password: the app password.

[seanaty]

Do you have a link to the page where that documentation is from for reference?

[Ruhan Coetzer]

Sure. https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/

Scroll to the bottom of the page.

My mistake was to use the label specified for the app password as the user name. One needs to use your regular user name and provide the app password. 

I think it would have been awesome if the email outlining  the change had these options/steps incorporated. 

[seanaty]

@Ruhan Coetzer 

Your link doesn't work and the documentation hasn't been updated. 

 Indeed it doesn't! It worked when I posted it but I've tracked its disappearance down to a documentation migration that just happened. On the plus side, I hope you'll be happy to hear that we are investing in our documentation.

I'll get it back up for you.

[Blaine Trimmell]

What about users that are using HTTPS and their Atlassian account is tried to  Google, Microsoft, or Apple account. How do you get it to work for those?

[seanaty]

@Blaine Trimmell You can create an app password in that case.

[Blaine Trimmell]

what do you use for the user name? The  Google, Microsoft, or Apple account or the Bitbucket user name?

[seanaty]

Bitbucket username.

[beef623]

In its current implementation, the app password really isn't useful. All of my interaction with git is from the command line and I'm constantly working from different machines. The app passwords are only viewable once, can't be set manually, aren't easy to type and aren't easy to remember. 

[tcowin]

Hey @seanaty -- I'm using SSH keys now to interact with the bitbucket via git -- do these keys need to change or does the password affecting the Website need to? I am unclear on this.

Also -- that link you gave out at the top gives me a 404 just now.

Thanks!

[seanaty]

The link at the top is queued to be deployed.

If you're using git with SSH then you don't need to do anything.