Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,483
Community Members
 
Community Events
185
Community Groups

Deprecating Atlassian account password for Bitbucket API and Git activity

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

2 answers

@seanaty  

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

0 votes
seanaty
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 03, 2021

This change is only affects Bitbucket Cloud.

@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?

seanaty
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 15, 2022

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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events