Following to the documentation at
the OAuth consumer can be added with a secret key and secret password starting from the avatar " Bitbucket settings." .
I have already accomplished this once. But now I have problems using these secrets on a command line shell based on composer.
Where is the "Bitbucket settings" now? Where must I set the OAuth consumer and check the secrets? Must they be activated somehow?
Hi Franz and welcome to the community.
I believe that the documentation page you linked is obsolete (I'll be checking this with my team internally).
OAuth is now associated with a Bitbucket workspace, and it can be found in a certain workspace's Settings instead.
You can find the relevant documentation here:
I am quoting from this documentation the steps to find the OAuth consumer option:
From your profile avatar in the bottom left, click on the workspace in the Recent workspaces list or click All workspaces to open an entire list from which to choose.
Click Settings on the left sidebar to open the Workspace settings.
Click OAuth consumers under Apps and features on the left navigation.
Click the Add consumer button.
Please feel free to let me know if you need any further help.
The 'Apps and features' menu item is not dependant on licensing. This option is visible only to the workspace owner for personal workspaces.
Allow me to explain with an example:
- Someone signs up for a Bitbucket Cloud account with username A.
- Bitbucket automatically creates a workspace for that user, with workspace-id A (this can be changed later)
- Then, the user creates additional workspaces B, C, D.
Workspace A is considered the user's personal workspace. If other users are added as admins, they won't be able to view 'Apps and features' for that workspace. Workspaces B, C, and D are not personal workspaces. If another user is added as an admin, they'll be able to view this option. We have a ticket about this in our issue tracker: https://jira.atlassian.com/browse/BCLOUD-20342
If you're an admin of such a workspace, you can ask the user associated with the workspace to create the OAuth consumer. If you want multiple admins to be able to access this option, you could create a new workspace manually, transfer any repos there and work with that new workspace.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
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