I can only find documentation for personal access token for Bitbucket Server: https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html
Is this functionality also available for Bitbucket Cloud?
What is the reason behind lack of *personal access tokens* feature in Bitbucket cloud?
As a developer, I find access tokens very handy when you are executing Git commands (i.e. clone, push, pull, etc). I use Github's personal access token on daily basis and it's super convenient.
I guess I will have to disable 2FA in my bitbucket :(
With help from AWS support I've been able to create an Amplify App using a CloudFormation template and the AWS::Amplify::App resource.
I set up an OAuth consumer and using the client_credentials flow I was able to get a short-lived access token. Once I adjusted the OAuth consumer permissions/scopes appropriately (repository:admin webhook pullrequest) then it allowed an access token with appropriate permissions to be using in the OauthToken CloudFormation parameter combined with the Repository parameter with the Repo URL.
This created an Amplify App linked to the BitBucket Repo. There's a bit more effort involved but it works.
Dear Allan Oliveir,
I have been trying to replicate your suggestion workflow for creating AWS Amplify app. However, I am having trouble generating an access_token from BitBucket following client_credentials flow or even getting an oauth_token.
Any assistance would be appreciated. Would be happy to provide any details needed.
So long as you've created an OAuth Consumer in your workspace with the correct permissions you should be able to generate short-lived access tokens as needed.
My implementation uses the https://bitbucket.org/site/oauth2/access_token endpoint with the key and secret and the client_credentials grant_type. An example below in Python.
response = requests.post(
Also with CURL it's straight forward to test e.g.
curl -X POST --user <OAuth consumer Key>:<OAuth consumer Secret> https://bitbucket.org/site/oauth2/access_token -d grant_type=client_credentials
Hope that helps, let me know if you need anymore guidance.
I have an issue. I am not able to use the Jenkins generated access token in the webhook over at Bitbucket. Secondly, because I am not able to generate a personal access token in the bitbucket cloud, I am not able to intgrate Jenkins continuously. Please help.
I am getting the error 403: No valid crumb issuer.
I have tried enabling CSRF protection and compatibility for proxies, but still upto no good. Please help.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events