This is no good for me, as I created various private repositories that I used as Composer packages, and then used a personal OAuth consumer to authenticate Composer with Bitbucket to be able to access all of these private repositories.
How am I supposed to do this now if Bitbucket is expecting me to create OAuth consumers for each workspace?!
Prior to introducing workspaces in Bitbucket Cloud, users could have repositories owned by either their individual Bitbucket account or by a team account.
Therefore, there was an option to create an OAuth consumer both in an account's Settings and also in a team's Settings.
After we introduced workspaces, a workspace was created automatically for every individual account and team account. Repositories are now owned by a certain workspace, a user's account is used for authentication and accessing Bitbucket.
Due to this change, you can find the OAuth option in the Settings of each workspace, as opposed to your personal account, and you can create the OAuth consumer there.
Apologies for the confusion caused by the documentation, I am going to open a ticket with our documentation team to have this corrected.
Please feel free to let me know if you have any questions.
Hi @Antoine Kurukchi ,
As long as the workspace exists, the OAuth consumer will still be valid and good to use.
The consumer is owned by the workspace it is created in. Even if you remove access from the user who created the consumer, it will still be valid.
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