Bitbucket Access Token results in "Error retrieving username 401 Unauthorized"

[sullikidoz]

Thanks for the implementation of Bitbucket Access Tokens!

Unfortunately, I haven't been able to successfully validate this feature. My repro steps:

Download the v1.1 tar for linux

1. Extract it
2. Create an Atlassian API token for Bitbucket at https://id.atlassian.com/manage-profile/security/api-tokens (I gave it all scopes just for testing)
3. export BITBUCKET_USERNAME=myusername and export BITBUCKET_TOKEN=ATATT_etc...
4. ./gitbackup -service bitbucket results in Error retrieving username401 Unauthorized
5. I can see that my API token was used "1 minute ago" so it appears to be the right kind of token. I've tried every variation of my username, but it should be Username indicated at https://bitbucket.org/account/settings/.

(I also tried creating a Bitbucket Access Token at https://bitbucket.org/kidozteam/workspace/settings/access-tokens but that got the same result and just said "Never Used" so presumably that's not the right kind of token).

Thanks for any help you can provide!

[amitsaha]

Hi @sullikidoz I will update our README, but for bitbucket, BITBUCKET_USERNAME=<your atlassian email>

From https://developer.atlassian.com/cloud/bitbucket/rest/intro/#authentication

To authenticate with an API token, use Basic HTTP Authentication as per RFC-2617, where the username is your Atlassian email and password is the API token.

Want to see if that works for you now?

[sullikidoz]

I swear I tried that yesterday, but it's working now!

My guess is that Atlassian's tokens take some time to deploy, so maybe this is just an issue of not waiting long enough?

Atlassian does say "New tokens may take up to a minute to work after they’ve been created." Though I certainly waited more than a minute.

Much appreciated!

[amitsaha]

thanks @sullikidoz