You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello, I was looking at the following article and had more questions on its effects:
We utilize the Bitbucket API to clone git repos. I believe we use the access token method (we are utilizing this library with it's default OAuth2 method: https://www.npmjs.com/package/bitbucket-api-v2\) but I was just wondering what affect this would have on our workflow? I don't believe it would effect us but I wanted to make sure we are all good.
I'm David and I work on the Bitbucket Cloud team as a software engineer.
The change could impact you depending on how you are generating those access tokens. Which OAuth 2.0 flow are you using? If you are using OAuth 2.0 Resource Owner Password Credentials Grant (4.3) to generate access tokens then this change will impact you.
Bitbucket Cloud no longers allows OAuth 2.0 Resource Owner Password Credentials Grant (4.3) flow. We do, however, still support the remaining three OAuth 2.0 (RFC-6749) grant flows, plus a custom Bitbucket flow for exchanging JWT tokens for access tokens.
I would recommend that you ensure that you are using one of the supported methods for getting access tokens for Bitbucket Cloud API authentication. You can find more details here on our API documentation page: https://developer.atlassian.com/cloud/bitbucket/rest/intro/#authentication