VSCODE-1050: PAT auth for hosted BitBucket(like for hosted Jira) #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Like the API of Jira and Bitbucket, the API of Bitbucket supports Bearer Auth using PAT instead of Basic Auth: https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html A number of other customers have expressed a need for this feature, not just us (Cloud Software Group): We disallow the use of HTTP Basic Auth for security reasons for the Confluence, Jira and Bitbucket APIs of our self-hosted services. Instead, we require the use of Bearer Auth using a PAT by the users. A background information for this is that, that your security policy requires 2FA or alternatively tokens, password authentication without a 2nd factor as implemented in HTTP Basic Authentication is prohibited by company security policy, and therefore HTTP Basic Authentication is prohibited. Also, by security policy, passwords have to be changed frequently, so even without that prohibition, password authentication would be very cumbersome as frequent changes result in frequent breakdown of the Atlascode login in VS Code. Right now, the Atlascloud plugin supports authenticating to Jira using PAT because of a requirement by a customer, but the same has not been extended to Bitbucket, it only supports using username/password (Basic Authentication). curl -v --oauth2-bearer $PAT https://<self-hosted bitbucket server>/rest/api/1.0/users/userslug?avatarSize=48 Bearer Authorization is already available in atlascode, but not yet enabled for Bitbucket, it just was requested for Jira and not for Bitbucket: https://bitbucket.org/atlassianlabs/atlascode/issues/237/allow-saml-sso-as-authentication-method All that remains for Atlascode is to allow Bearer Authorization for Bitbucket as well. This is what this PR does. It adds the same option to alternatively use PAT auth for self-hosted Bitbucket like the Jira client of Atlascode already implements. Signed-off-by: Bernhard Kaindl <bernhard.kaindl@gmx.de>
bkaindl
requested review from
bwieger-atlassian-com,
sdzh-atlassian and
cabella-dot
as code owners
|
Hi @bkaindl! Thank you for resubmitting the PR - and once again, sorry for the trouble you experienced with CLA 🙏 The change itself looks good to me - let me get a second pair of eyes on it (per policy 😉) and we'll see if we can roll it into our new nightly pre-releases. For @atlassian/axon - CI didn't run here:
|
bwieger-atlassian-com
requested changes
Dec 13, 2024
|
Addressing comments in #41 |
bwieger-atlassian-com
added a commit
that referenced
this pull request
Dec 17, 2024
* Patch 1 (#42) * VSCODE-1050: PAT auth for hosted BitBucket(like for hosted Jira) Like the API of Jira and Bitbucket, the API of Bitbucket supports Bearer Auth using PAT instead of Basic Auth: https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html A number of other customers have expressed a need for this feature, not just us (Cloud Software Group): We disallow the use of HTTP Basic Auth for security reasons for the Confluence, Jira and Bitbucket APIs of our self-hosted services. Instead, we require the use of Bearer Auth using a PAT by the users. A background information for this is that, that your security policy requires 2FA or alternatively tokens, password authentication without a 2nd factor as implemented in HTTP Basic Authentication is prohibited by company security policy, and therefore HTTP Basic Authentication is prohibited. Also, by security policy, passwords have to be changed frequently, so even without that prohibition, password authentication would be very cumbersome as frequent changes result in frequent breakdown of the Atlascode login in VS Code. Right now, the Atlascloud plugin supports authenticating to Jira using PAT because of a requirement by a customer, but the same has not been extended to Bitbucket, it only supports using username/password (Basic Authentication). curl -v --oauth2-bearer $PAT https://<self-hosted bitbucket server>/rest/api/1.0/users/userslug?avatarSize=48 Bearer Authorization is already available in atlascode, but not yet enabled for Bitbucket, it just was requested for Jira and not for Bitbucket: https://bitbucket.org/atlassianlabs/atlascode/issues/237/allow-saml-sso-as-authentication-method All that remains for Atlascode is to allow Bearer Authorization for Bitbucket as well. This is what this PR does. It adds the same option to alternatively use PAT auth for self-hosted Bitbucket like the Jira client of Atlascode already implements. Signed-off-by: Bernhard Kaindl <bernhard.kaindl@gmx.de> * Update clientManager.ts --------- Signed-off-by: Bernhard Kaindl <bernhard.kaindl@gmx.de> Co-authored-by: Bernhard Kaindl <bernhard.kaindl@gmx.de> * lint * update .vscodeignore to not include test files --------- Signed-off-by: Bernhard Kaindl <bernhard.kaindl@gmx.de> Co-authored-by: Bernhard Kaindl <bernhard.kaindl@gmx.de>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re-submit of #22 because of the SLA issue
Like the API of Jira and Bitbucket, the API of Bitbucket supports Bearer Auth using PAT instead of Basic Auth:
https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html
A number of other customers have expressed a need for this feature, not just us (Cloud Software Group): We disallow the use of HTTP Basic Auth for security reasons for the Confluence, Jira and Bitbucket APIs of our self-hosted services. Instead, we require the use of Bearer Auth using a PAT by the users.
A background information for this is that, that your security policy requires 2FA or alternatively tokens, password authentication without a 2nd factor as implemented in HTTP Basic Authentication is prohibited by company security policy, and therefore HTTP Basic Authentication is prohibited.
Also, by security policy, passwords have to be changed frequently, so even without that prohibition, password authentication would be very cumbersome as frequent changes result in frequent breakdown of the Atlascode login in VS Code.
Right now, the Atlascloud plugin supports authenticating to Jira using PAT because of a requirement by a customer, but the same has not been extended to Bitbucket, it only supports using username/password (Basic Authentication).
curl -v --oauth2-bearer $PAT https:///rest/api/1.0/users/userslug?avatarSize=48
Bearer Authorization is already available in atlascode, but not yet enabled for Bitbucket, it just was requested for Jira and not for Bitbucket:
https://bitbucket.org/atlassianlabs/atlascode/issues/237/allow-saml-sso-as-authentication-method
All that remains for Atlascode is to allow Bearer Authorization for Bitbucket as well.
This is what this PR does. It adds the same option to alternatively use PAT auth for self-hosted Bitbucket like the Jira client of Atlascode already implements.