Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support OAuth v2 for Bitbucket Server #21949

Closed
Tracked by #21941
RickJWagner opened this issue Jan 23, 2023 · 3 comments
Closed
Tracked by #21941

Support OAuth v2 for Bitbucket Server #21949

RickJWagner opened this issue Jan 23, 2023 · 3 comments
Assignees
Labels
area/che-server kind/enhancement A feature request - must adhere to the feature request template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system. status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Milestone

Comments

@RickJWagner
Copy link
Contributor

RickJWagner commented Jan 23, 2023

Is your enhancement related to a problem? Please describe

Users want to use OAuth 2.0 with BitBucket.

Describe the solution you'd like

Support OAuth2, as we do for Git:
https://www.eclipse.org/che/docs/stable/administration-guide/configuring-oauth-2-for-github/

Instead of just OAuth1, as we currently provide for BitBucket:
https://www.eclipse.org/che/docs/stable/administration-guide/configuring-oauth-1-for-a-bitbucket-server/

Additional context

Enterprise customers are making the request, please give it good consideration. Thank you!

Release Notes Text

Atlassian Bitbucket Server has recently added the support for OAuth v2.0 for access delegation (previously only OAuth v1 was supported). Eclipse Che now supports both OAuth v2.0 and v1.0 applications to automatically mount and configure developers Bitbucket personal access tokens.

@RickJWagner RickJWagner added the kind/enhancement A feature request - must adhere to the feature request template. label Jan 23, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jan 23, 2023
@vinokurig vinokurig self-assigned this Jan 23, 2023
@ibuziuk ibuziuk added severity/P1 Has a major impact to usage or development of the system. team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che area/che-server and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jan 23, 2023
@ibuziuk ibuziuk mentioned this issue Feb 15, 2023
56 tasks
@l0rd l0rd added new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording labels Feb 16, 2023
@l0rd l0rd changed the title Please add support for OAuth 2.0, needed by BitBucket OAuth v2.0 BitBucket Support Feb 16, 2023
@l0rd l0rd added this to the 7.61 milestone Feb 16, 2023
@l0rd
Copy link
Contributor

l0rd commented Feb 16, 2023

@vinokurig can we close this issue as completed?

@vinokurig
Copy link
Contributor

There is an unmerged docs PR, so I believe we have to wait until it's merged.

@l0rd l0rd changed the title OAuth v2.0 BitBucket Support Support OAuth v2.0 for Bitbucket Server Feb 18, 2023
@l0rd l0rd changed the title Support OAuth v2.0 for Bitbucket Server Support OAuth v2 for Bitbucket Server Feb 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server kind/enhancement A feature request - must adhere to the feature request template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system. status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Projects
None yet
Development

No branches or pull requests

6 participants