> ## 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 a Confluence Data Center connector

> C1 provides identity governance and just-in-time provisioning for Confluence Data Center. Integrate your Confluence 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" /> | <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" /> |
| Spaces   | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |

The Confluence Data Center connector supports [automatic account provisioning](/product/admin/account-provisioning).

This connector does not support account deprovisioning. You must deprovision accounts directly in Confluence Data Center.

## Gather Confluence Data Center credentials

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

<Warning>
  **Important**

  A user with **Administrator** access in Confluence Data Center must perform this task.
</Warning>

### Create an API token

<Steps>
  <Step>
    Log into your Confluence Data Center account with Administrator access.
  </Step>

  <Step>
    Navigate to [https://id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens).
  </Step>

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

  <Step>
    Give your token a label, such as **C1**, and click **Create**.
  </Step>

  <Step>
    Carefully copy and save the newly generated API token.
  </Step>
</Steps>

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

## Configure the Confluence 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 Confluence 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 Confluence Data Center connector, 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-confluence-datacenter): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new Confluence 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 Confluence 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 Confluence Data Center connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-confluence-datacenter-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-confluence-datacenter-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # Confluence Data Center credentials
      BATON_ACCESS_TOKEN: <Access token for your Confluence Data Center account>
      BATON_HOSTNAME: <URL of your Confluence Data Center instance>
      BATON_USERNAME: <Username for Confluence Data Center account>
      BATON_PASSWORD: <Password for Confluence Data Center account>

      # 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-confluence-datacenter.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-confluence-datacenter
      labels:
        app: baton-confluence-datacenter
    spec:
      selector:
        matchLabels:
          app: baton-confluence-datacenter
      template:
        metadata:
          labels:
            app: baton-confluence-datacenter
            baton: true
            baton-app: confluence-datacenter
        spec:
          containers:
          - name: baton-confluence-datacenter
            image: ghcr.io/conductorone/baton-confluence-datacenter:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-confluence-datacenter
            envFrom:
            - secretRef:
                name: baton-confluence-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 Confluence Data Center connector to. Confluence Data Center data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

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