Starting Mar 1, 2022, Bitbucket users will no longer be able to use their Atlassian account password to interact with Bitbucket via Git over https and the Bitbucket API. Users will need to start using Bitbucket app passwords for Git commands, scripts, and integrating tools.
As part of an ongoing effort to align with internal infrastructure and improve Atlassian account security, Bitbucket offers app passwords, which are substitute passwords for a user account, designed to be used for a single purpose with limited permissions. App passwords can be used to run Git commands over https to a user’s Bitbucket account and to integrate Bitbucket with other tools like Sourcetree and Bamboo.
On March 1, 2022 Bitbucket users will no longer be able to use their Atlassian account password to interact with Bitbucket via Git over https and the Bitbucket API, and will need to switch to app passwords.
How can I tell if I will be affected by this change?
We’ll be contacting teams and users based on what we find in our logs for Atlassian account password usage. If you currently use your Atlassian account password for any Git or Bitbucket API activity, you can start proactively using Bitbucket app passwords at any time prior to the date mentioned above.
How to migrate
To create an app password:
- From your profile and settings avatar, select Personal settings.
- Select App passwords under Access management.
- Select Create app password.
- Give the app password a name related to the application that will use the password.
- Select the specific access and permissions you want to assign to this application password.
- Copy the generated password and either record or paste it into the application you want to give access. The password is only displayed this one time.
More details on app passwords (including usage and revocation) can be found in Bitbucket documentation.