> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up an Atlassian Bitbucket Data Center connector

> C1 provides identity governance and just-in-time provisioning for Bitbucket Data Center. Integrate your Bitbucket Data Center instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

## Capabilities

| Resource      | Sync                                                          | Provision                                                     |
| :------------ | :------------------------------------------------------------ | :------------------------------------------------------------ |
| Accounts      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Projects      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Repositories  | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Groups        | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Organizations | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |

## Gather Bitbucket Data Center credentials

Configuring the connector requires you to pass in credentials generated in Bitbucket Data Center. Gather these credentials before you move on.

### Create an HTTP token

<Steps>
  <Step>
    In Bitbucket, click your profile in the top right corner of the screen and navigate to **Manage account** > **HTTP access tokens**.
  </Step>

  <Step>
    Click **Create token**.
  </Step>

  <Step>
    Give the token a name, such as "C1".
  </Step>

  <Step>
    In the **Permissions** section of the page, select these permissions:

    * Project: Admin
    * Repository: Admin
  </Step>

  <Step>
    Click **Create**.
  </Step>

  <Step>
    Your new token is shown. Carefully copy and save the token.
  </Step>
</Steps>

**Done.** Next, move on to the connector configuration instructions.

## Configure the Bitbucket Data Center connector

<Warning>
  **To complete this task, you'll need:**

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of Bitbucket Data Center credentials generated by following the instructions above
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    Cloud-hosted connector not currently available.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Bitbucket Data Center]\([https://github.com/conductorone/baton-bitbucket-datacenter](https://github.com/conductorone/baton-bitbucket-datacenter)), hosted and run in your own environment.**

    When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

    ### Resources

    * [GitHub repository](https://github.com/conductorone/baton-adobe): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new Bitbucket Data Center connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Bitbucket Data Center connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
        * Add the connector to a managed app (select from the list of existing managed apps)
        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.
        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.
        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Bitbucket Data Center connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-bitbucket-datacenter-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-bitbucket-datacenter-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # Bitbucket Data Center credentials
      BATON_BITBUCKETDC_BASEURL: <Full URL of your Bitbucket Data Center Server (such as http://localhost:7990)>
      BATON_BITBUCKETDC_TOKEN: <Bitbucket HTTP access token>
      BATON_USERNAME: <Username of Bitbucket administrator>

      # Optional: include if you want C1 to provision access using this connector
      BATON_PROVISIONING: true
    ```

    See the connector's README or run `--help` to see all available configuration flags and environment variables.

    #### Deployment configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-bitbucket-datacenter.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-bitbucket-datacenter
      labels:
        app: baton-bitbucket-datacenter
    spec:
      selector:
        matchLabels:
          app: baton-bitbucket-datacenter
      template:
        metadata:
          labels:
            app: baton-bitbucket-datacenter
            baton: true
            baton-app: bitbucket-datacenter
        spec:
          containers:
          - name: baton-bitbucket-datacenter
            image: ghcr.io/conductorone/baton-bitbucket-datacenter:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-bitbucket-datacenter
            envFrom:
            - secretRef:
                name: baton-bitbucket-datacenter-secrets
    ```

    ### Step 3: Deploy the connector

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Bitbucket Data Center connector to. Bitbucket Data Center data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

    **Done.** Your Bitbucket Data Center connector is now pulling access data into C1.
  </Tab>
</Tabs>