diff options
| author | Philippe Perrin <philippe.perrin@sonarsource.com> | 2022-08-26 16:51:20 +0200 |
|---|---|---|
| committer | sonartech <sonartech@sonarsource.com> | 2022-08-29 20:02:52 +0000 |
| commit | 4d1bd03543c55e564151d55e3a4763b82bc8e512 (patch) | |
| tree | dae8e3c614837286a622fde1cc2cbb359ca4ff7d /server/sonar-docs/src/pages/analysis/bitbucket-cloud-integration.md | |
| parent | df8d5def80fa3abcef563310aa93b22d70cf4d37 (diff) | |
| download | sonarqube-4d1bd03543c55e564151d55e3a4763b82bc8e512.tar.gz sonarqube-4d1bd03543c55e564151d55e3a4763b82bc8e512.zip | |
SONAR-17231 Move DevOps platform related authentication information to the newly created authentication section
Diffstat (limited to 'server/sonar-docs/src/pages/analysis/bitbucket-cloud-integration.md')
| -rw-r--r-- | server/sonar-docs/src/pages/analysis/bitbucket-cloud-integration.md | 21 |
1 files changed, 1 insertions, 20 deletions
diff --git a/server/sonar-docs/src/pages/analysis/bitbucket-cloud-integration.md b/server/sonar-docs/src/pages/analysis/bitbucket-cloud-integration.md index 74148fe21e3..7653c46c198 100644 --- a/server/sonar-docs/src/pages/analysis/bitbucket-cloud-integration.md +++ b/server/sonar-docs/src/pages/analysis/bitbucket-cloud-integration.md @@ -300,24 +300,5 @@ SonarQube can also report your Quality Gate status to Bitbucket Cloud pull reque | When adding a Quality Gate status to your pull requests, individual issues will be linked to their SonarQube counterparts automatically. For this to work correctly, you need to set the instance's **Server base URL** (**[Administration > Configuration > General Settings > General > General](/#sonarqube-admin#/admin/settings/)**) correctly. Otherwise, the links will default to `localhost`. ## Authenticating with Bitbucket Cloud -To allow users to log in with Bitbucket Cloud credentials, you need to use an [OAuth consumer](https://support.atlassian.com/bitbucket-cloud/docs/use-oauth-on-bitbucket-cloud/) and set the authentication settings in SonarQube. You can either use the OAuth consumer that you created above in the **Importing your Bitbucket Cloud repositories into SonarQube** section or create a new OAuth consumer specifically for authentication. See the following sections for more on setting up authentication. -### Setting your OAuth consumer settings -Create or update your OAuth consumer in your Bitbucket Cloud workspace settings and specify the following: - -- **Name** – the name of your OAuth consumer. -- **Callback URL** – your SonarQube instance URL. -- **Permissions**: - * **Account**: **Read** and **Email** access. - * **Workspace membership**: **Read** access. - -[[info]] -| If you're using the same OAuth consumer for authentication and importing projects/reporting status to pull requests, make sure that the **This is a private consumer** box is checked and **Read** access for the **Pull requests** permission is granted. - -### Setting your authentication settings in SonarQube -To set your global authentication settings, navigate to **Administration > Configuration > General Settings > Authentication > Bitbucket Cloud Authentication** and update the following settings: - -- **Enabled** - set to true. -- **OAuth consumer key** - enter the **Key** from your OAuth consumer page in Bitbucket. -- **OAuth consumer secret** - enter the **Secret** from your OAuth consumer page in Bitbucket. -- **Workspaces** - Only users from Bitbucket Workspaces that you add here will be able to authenticate in SonarQube. This is optional, but _highly_ recommended to ensure only the users you want to log in with Bitbucket credentials are able to. +See [Authenticating with Bitbucket Cloud](/instance-administration/authentication/bitbucket-cloud/)
\ No newline at end of file |