I have an application that does rest calls to both Jira and Bitbucket. For authorization, it takes your username + password, encodes it, and uses it as part of basic authentication on the requests.
That broke on new accounts a few weeks ago, due to the username:password being deprecated, at least for Jira.
I fixed the Jira side by getting an Atlassian token and using that, so the authentication is now username:token (encoded). No problem talking to Jira.
HOWEVER, I can no longer talk to Bitbucket. Using that token results in authentication errors. Trying to set up a separate username:password authentication also fails on Bitbucket, UNLESS I use my very old password (about 4 passwords ago).
For instance, I’m trying a simple GET https://api.bitbucket.org/2.0/user call with the Chrome Advanced REST Client.
If the authentication is not right, it fails with 401 unauthorized. I’ve tried:
- basic: username + Atlassian token ==> fail
- basic: username + current password ==> fail
- basic: username + really old password ==> success
- basic: username + app password from bitbucket ==> fail
- token: app password from bitbucket ==> fail, saying my token has expired
Anyone have ideas on how I can either
a) use the Atlassian token for authentication on both jira and bitbucket?
b) use something from bitbucket for authentication on bitbucket?