migrating from Bitbucket App Passwords to API Tokens

[Karandeep Singh]

Hi Atlassian Support,

We are migrating from Bitbucket App Passwords to API Tokens as required by the CHANGE-3222 deprecation deadline (July 28, 2026).

We are trying to authenticate Jenkins with Bitbucket over HTTPS using a Personal API Token but keep getting authentication failures.

Setup details:
- Jenkins Git Plugin (latest)
- Repository URL: https://bitbucket.org/SymTrain/jenkins-pipelines.git
- Credential type: Username with password
- Username tried: x-bitbucket-api-token-auth (as per Atlassian docs)
- Username tried: Atlassian account email
- Username tried: Bitbucket username
- Password: Personal API Token generated from id.atlassian.com

Error received:
fatal: Authentication failed for 'https://bitbucket.org/SymTrain/jenkins-pipelines.git/'

[prabhakaran_p4]

Hi @Vipul Reddy , @Arkadiusz Wroblewski  

Same issues we are also facing at our end. 

Setup details:
- Jenkins Git Plugin (latest)
- Repository URL: https://SysTestAuto@bitbucket.org/<TeamName>/<RepoName>.git

- Credential type: Username with password
- Username tried: x-bitbucket-api-token-auth (as per Atlassian docs)
- Username tried: Atlassian account email
- Username tried: Bitbucket username
- Password: Personal API Token generated from id.atlassian.com

Sometime with above all changes are working and same after few hrs its not working, Trying to understand how we are confirm the call is getting authenticated in using Password or App Token.

[prabhakaran_p4]

@Vipul Reddy @Arkadiusz Wroblewski 

Error message  : - 
ERROR: Error cloning remote repo 'origin'

> C:\Program Files\Git\bin\git.exe fetch --tags --force --progress -- https://SysTestAuto@bitbucket.org/<TeamID>/<RepoName>.git +refs/heads/*:refs/remotes/origin/* # timeout=10
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Command "C:\Program Files\Git\bin\git.exe fetch --tags --force --progress -- https://SysTestAuto@bitbucket.org/<TeamID>/<RepoName>.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout:
stderr: remote: CHANGE-3222 - Functionality has been deprecated
remote: App passwords are deprecated and must be replaced with API tokens.

[Arkadiusz Wroblewski]

Hello @Karandeep Singh 

Your token are Scoped or not ?

Best,

Arkadiusz 🤠 

[Karandeep Singh]

Hi Arkadiusz

Yes I tried with scoped tokens as well, but I'm still getting same issue

Best,
Karandeep

[Vipul Reddy]

Hello Karandeep,

Thanks for the comprehensive details, and the update to Arkadiusz. Just so that we have covered everything, could you please confirm if you're performing the following:

1. Create the correct token type:

• Go to id.atlassian.com → Security → Create and manage API tokens

• Select "Create API token with scopes" (not the classic "Create API token")

• Name the token and set an expiry

• Select Bitbucket as the app

• Grant the required scopes (add anything else you require):

  • read:repository:bitbucket — for cloning/fetching

  • write:repository:bitbucket — for pushing

2. Configure Jenkins credentials:

• Kind: Username with password

• Username: x-bitbucket-api-token-auth

• Password: The new scoped API token

Can you please try the steps above and let us know the outcome?

Thanks!

[Kelvin Depena]

i was told by atlassian support that "for API tokens, the username must be the Atlassian account email address." The x-bitbucket-api-token-auth username is not working.