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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi!
I am trying to managed my Bitbucket Cloud Workspace by the API using a oauth consumer but I have just found out that there are a few endpoints where I must use app password:
- Update group permissions for a repository
- Update user permissions for a repository
The thing is, app password are own by an account meanwhile oauth consumer can be created at workspace level. The idea is not to use personal accounts because at some point these accounts can be deleted and generate a problem in the autommation so instead we would rather use the oauth from the workspace that is going to be always active.
Therefore, this two endpoint are a big problem for us due to we cannot access by oauth. I wanted to ask if this can be solved by a workaround or if there is some plan to allow to access these endpoints by oauth? Maybe an other solution could be allow to create app passwords at workspace level.
Hello @mgnavarrete ,
Thanks for reaching out to Atlassian Community!
I'm afraid that currently, the repository permissions endpoints indeed don't support using OAuth tokens for authentication, only app passwords. We do have a feature request to add the ability to authenticate with OAuth consumers for those endpoints, which you can check in the following link :
I would suggest you to add your vote there, since this helps both developers and product managers to understand the interest. Also, make sure you add yourself as a watcher in case you want to receive first-hand updates from that ticket. Please note that all features are implemented with this policy in mind.
Unfortunately, there's no workaround at this moment other than using App Passwords for authentication.
Thank you, @mgnavarrete !
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.