Does the Deprecating Atlassian account password for Bitbucket API and Git activity will affect the Bitbucket server users account passwords and the authentication from Bamboo server to Bitbucket server in Linked Repositories
We are using bitbucket as maven repository for storing libraries .
In the bitbucket pipelines in order to fetch these libraries we are using settings.xml were we store the credentials as shown below :
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
<servers>
<server>
<id>bitbucket.downloads</id>
<username>username@xxxxxxxx.com</username>
<password><defaultAccountPassword></password>
</server>
</servers>
<profiles>
<profile>
<id>bitbucket-downloads</id>
<repositories>
<repository>
<id>bitbucket.downloads</id>
<name>bitbucket downloads</name>
<url>bitbucket://xxxxxxxxx/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>bitbucket-downloads</activeProfile>
</activeProfiles>
</settings>
Are we going to be able still to use this approach after 1 of March or we need to change the implementation and use app password instead.
thanks in advance
This change is only affects Bitbucket Cloud.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@seanaty I use my Atlassian id to configure my bitbucket repositories in Jenkins and my local machine. Will this change affect my access to these repositories?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Access to repos is not changing. But you may in fact need to make a (quite simple IMO) change if you don't want any interruption and you're free to make that change now.
Say you're using curl to access the API.
Instead of doing this:
curl -u my-username:my-password https://api.bitbucket.org/2.0/my-username/repositories
you'd do this:
curl -u my-username:my-brand-new-app-password https://api.bitbucket.org/2.0/my-username/repositories
So you'll need to swap out "my-password" with "my-brand-new-app-password"
Going forward you password will be only for creating an interaction session on bitbucket.org (the website) and all other forms of authentication (git, API) will require an app password.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.