nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Only possible to switch to API Token when username is switched to e-mail

R J Janssen

I created an API key in Bitbucket as indicated in the Sourcetree documentation with scopes as indicated.

Then in Sourcetree I wanted to change my account (with existing username) over to API Token. I entered my correct e-mail below the dropdown and set my existing username in the dialog that follows. But then the API key is not recognized and error 'Failed to get user details, You do not have permission to access URL etc. request returns with status Unauthorized.

The only way to let the API token be accepted is when I set the username to my e-mail address. But then of course no repository actions will work anymore.

Removing old entries in Credential Manager (I am doing this on Windows) did not solve the problem.

How to solve this, now unable to use Sourcetree ;-[

Accepted answers

Tinker Fadoua

@R J Janssen

Can you try what was already recommended here?

https://community.atlassian.com/forums/Bitbucket-questions/Having-trouble-switching-to-API-tokens/qaq-p/3213684

Best,

Fadoua

All comments

Tomislav Tobijas

Hey @R J Janssen ,

Are we talking about Bitbucket on-prem or cloud? Also, when you say

...no repo actions will work anymore...

what do you mean by that? 🤔 Are we talking about authentication under Tools → Options → Authentication succeeds after changing the username to your email address, but operations such as fetch/pull/push against an existing repository then fail?
If so, can you share which error do you get?

Generally speaking:

App Password = Bitbucket username + App Password.
API Token = Atlassian account email + API Token

Note that existing Git credentials can sometimes still be cached separately.

I would also check/remove any existing Bitbucket credentials from Windows Credential Manager (as you did) and verify the repository's configured remote URL under Repository Settings → Remotes. 👀

Cheers,
Tobi

R J Janssen

To avoid the problem I

Removed all git* entries in Credential Manager
Added an account switching to oAuth with the existing username.

But then pushing fails with:

remote: CHANGE-3222 - Functionality has been deprecated
remote: App passwords are deprecated and must be replaced with API tokens.
remote: https://developer.atlassian.com/cloud/bitbucket/changelog#CHANGE-3222
fatal: unable to access 'https://bitbucket.org/RoelofSandP/xmaps_portal.git/': The requested URL returned error: 410