> ## 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 Databricks connector

> C1 provides identity governance and just-in-time provisioning for Databricks. Integrate your Databricks 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" /> |
| Roles              | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Service principals | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Workspaces         | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |

The Databricks connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning).

## Gather Databricks credentials

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

<Warning>
  A user with the **Account admin** role in each Databricks workspace you want to sync must perform this task.
</Warning>

### Look up your Databricks account ID

<Steps>
  <Step>
    Ensure that your Databricks user account has the **Account admin** role and is assigned to each Databricks workspace you want to sync to C1.
  </Step>

  <Step>
    In the Databricks account console, open the menu that appears next to your username in the upper right corner.
  </Step>

  <Step>
    Carefully and copy and save account ID.
  </Step>
</Steps>

### Generate Databricks credentials

You have three authentication choices when setting up the Databricks connector:

* **OAuth** (syncs info from all Databricks workspaces)

  <Steps>
    <Step>
      Follow the [Databricks OAuth authentication documentation](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html) to create a service principal and create an OAuth secret.
    </Step>

    <Step>
      Carefully copy and save the OAuth client ID and secret.
    </Step>
  </Steps>

* **Personal access token** (syncs info from a single Databricks workspace)

  <Steps>
    <Step>
      In Databricks, navigate to **Settings** > **Developer** > **Access tokens** and click **Manage**.
    </Step>

    <Step>
      Click **Generate new token** and create a new token.
    </Step>

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

* **Username and password** (syncs info from all Databricks workspaces)

  You do not need to generate any additional credentials to use this method.

**Done.** Here's the set of credentials you'll need when setting up the connector:

* Account ID
* OAuth client ID
* OAuth client secret

OR

* Account ID
* Personal access token
* Workspace ID for the Databricks workspace you're syncing

OR

* Account ID
* Username
* Password

Next, move on to the instructions for your chosen setup method.

## Configure the Databricks connector

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

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of Databricks 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.**

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

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

      <Step>
        Choose how to set up the new Databricks 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>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Select whether you're authenticating with **OAuth**, a **Personal access token**, or your **Username and password**.
      </Step>

      <Step>
        Paste the account ID you looked up in Step 1 into the **Account ID** field.
      </Step>

      <Step>
        Enter the required OAuth, token, or username and password credentials into the other two fields.
      </Step>

      <Step>
        **Google Cloud Platform and Azure Databricks customers only:** Enter your Databricks account hostname and hostname in the relevant fields.

        * For more on how to look up these values for GCP, see the GCP Databricks [REST API reference](https://docs.databricks.com/api/gcp/account/introduction) and [identifiers for workspace objects](https://docs.gcp.databricks.com/en/workspace/workspace-details.html) documentation.
        * For more on how to look up these values for Azure Databricks, see the the Azure Databricks [REST API reference](https://docs.databricks.com/api/azure/account/introduction) and [identifiers for workspace objects](https://learn.microsoft.com/en-us/azure/databricks/workspace/workspace-details) documentation.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Databricks connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Databricks 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

    * [Official download center](https://dist.conductorone.com/ConductorOne/baton-databricks): For stable binaries (Windows/Linux/macOS) and container images.

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

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

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-databricks-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-databricks-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # Databricks credentials, option 1
      BATON_ACCOUNT_ID: <Databricks account ID>
      BATON_DATABRICKS_CLIENT_ID: <OAuth client ID>
      BATON_DATABRICKS_CLIENT_SECRET: <OAuth client secret>

      # Databricks credentials, option 2
      BATON_ACCOUNT_ID: <Databricks account ID>
      BATON_WORKSPACE_TOKENS: <Personal access token>
      BATON_WORKSPACES: <Workspace ID for the Databricks workspace you're syncing>

      # Databricks credentials, option 3
      BATON_ACCOUNT_ID: <Databricks account ID>
      BATON_USERNAME: <Username for the Databricks account>
      BATON_PASSWORD: <Password for the Databricks 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-databricks.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-databricks
      labels:
        app: baton-databricks
    spec:
      selector:
        matchLabels:
          app: baton-databricks
      template:
        metadata:
          labels:
            app: baton-databricks
            baton: true
            baton-app: databricks
        spec:
          containers:
          - name: baton-databricks
            image: ghcr.io/conductorone/baton-databricks:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-databricks
            envFrom:
            - secretRef:
                name: baton-databricks-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 Databricks connector to. Databricks data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

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