Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

No more Oauth in Personal Settings

Tran Tien dung
Contributor
July 15, 2020

I'm looking for create Oauth consumer in Personal Settings as this link, but it's missing. Last year, I can create Oauth consumer and they still working.

personal settings.jpg

Any ideas or what might causing this issue?

3 answers

1 vote
Martin Bean
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 15, 2021

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?!

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 4, 2020

Hello,

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.

Kind regards,
Theodora

Antoine Kurukchi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 10, 2021

Can I just clarify something. When an OAuth Comsumer is created in the workspace and the user who created it leaves the team, the entry is still valid and good to use?

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 12, 2021

Hi @Antoine Kurukchi , I'll follow up on this with the development team as I'm not sure, and I will let you know.

Like • Antoine Kurukchi likes this
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 23, 2021

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.

Kind regards,
Theodora

0 votes
Deleted user July 17, 2020

Same thing, I can see them under workspaces but not under personal settings.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events