Unable to authenticate with Bitbucket since moving to API tokens!

Question

I switched to API token this morning as we are told app passwords are depreciated and we are forced to move this way. However since doing this I'm totally locked out from bitbucket via SourceTree! I have tried absolutely everything!

Deleted passwd file

Tried both email address and user addy in combination with API Token and my password. No combination hits.

I'm getting Authentication failed. Failed to get user details. You do not have permission to access URL https://api.bitbucket.org/2.0/user.

Well this is just stupid! What the hell am I meant to do. I've delete and reset token multiple times, changed my password. Reinstalled, deleted files. Such a terrible system I'm seriously thinking of shifting all our stuff to Github and be done with it.

If anyone has any ideas, otherwise I'll plan to start migrating next week as it is holding our work up.

stso · Answer

May be relevant

https://jira.atlassian.com/browse/BCLOUD-23928

Tomislav Tobijas · Answer

Glad at least there are some updates about this (even if you actually got back to the initial problem).

...I have now got a different error which is around what permissions I should give in the API scope...

I think your API token should include full repo scope, not just read or write, but the entire repo permission.

Also, is your remote URL HTTPS? Note that API tokens do not work with SSH.

I've just tested this and I got it working with the following setup (I've used Bitbucket cloud):

* Preferred Protocol: HTTPS
* Authentication: Basic
* Username: Atlassian Account email

After clicking on "Refresh App Password", in the prompt for "Password", I've added the newly created API token. 👇

Note that I've created an API token via https://id.atlassian.com/manage-profile/security/api-tokens > Create API token with scopes

* App: Bitbucket
* Select all Bitbucket scopes (I mean, I haven't tried it with only partial scopes)

I haven't worked or troubleshooted that much those issues with credential managers so I'm not sure what else you could check :/

Ed Williams_brr77k · Answer

@Tomislav Tobijas I have now got this working finally. However I'm still getting a login prompt when I try to push. Which was the original problem I had last night after installing Git LFS. It keeps looping credentialhelperselection dialogue and regardless what combination of details I put in. It just loops :/