> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-community-build/instance-administration/authentication/bitbucket-cloud.md).

# Bitbucket Cloud

Setting up the Bitbucket Cloud authentication in your SonarQube Server instance.

To allow users to log in with Bitbucket Cloud credentials, you need to use an [OAuth client](https://support.atlassian.com/bitbucket-cloud/docs/use-oauth-on-bitbucket-cloud/) and set the authentication settings in SonarQube Community Build. See the following sections for more on setting up authentication.

## Setting your OAuth client settings <a href="#setting-your-oauth-consumer-settings" id="setting-your-oauth-consumer-settings"></a>

Create your OAuth client in your Bitbucket Cloud workspace settings and specify the following:

* On the **Details** tab, **Name**: The name of your OAuth client.
* On the **Authorization** tab:
  * **Supported grant types**: Select **Authorization code**.
  * **Callback URLs**: `<Your SonarQube Community Build URL>/oauth2/callback/bitbucket`. For example, `https://sonarqube.mycompany.com/oauth2/callback/bitbucket`.
* On the **Scopes** tab:
  * **Account**: **Read** and **Email** access.
  * **Workspace membership**: **Read** access.

## Setting your authentication settings in SonarQube Community Build <a href="#setting-your-authentication-settings-in-sonarqube" id="setting-your-authentication-settings-in-sonarqube"></a>

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 **Client ID** of your OAuth client in Bitbucket Cloud.
* **OAuth consumer secret**: Enter the **Secret** of your OAuth client in Bitbucket Cloud.
* **Allow users to sign up**: enable to allow new users to authenticate. When disabled, only existing users will be able to authenticate to the server.
* **Workspaces**: Only users from Bitbucket Workspaces that you add here will be able to authenticate in SonarQube Community Build. This is optional but *highly* recommended to ensure only the users you want to log in with Bitbucket credentials are able to.

{% hint style="warning" %}
If the allowed workspaces are not entered, any user with a BitBucket account can log in to the SonarQube Community Build instance (assuming **Allow users to sign up** is set to true).
{% endhint %}

## Bitbucket Cloud group synchronization <a href="#bitbucket-cloud-group-synchronization" id="bitbucket-cloud-group-synchronization"></a>

Group synchronization is not supported for Bitbucket.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-community-build/instance-administration/authentication/bitbucket-cloud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.