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

> C1 provides identity governance for Box. Integrate your Box 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" /> |           |
| Groups      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Enterprises | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

## Gather Box credentials

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

<Warning>
  **Important**

  A user with an administrator role in Box and two-factor authentication set on their Box account must perform this task.
</Warning>

### Create a new Box custom app

<Steps>
  <Step>
    Log into the Box Developer Console.
  </Step>

  <Step>
    Click **Create New App** and select **Custom App**.
  </Step>

  <Step>
    Enter a name for your new app, such as "C1", and choose how to categorize the new app.
  </Step>

  <Step>
    When prompted to choose an authentication method for your new app, select **Server Authentication (Client Credentials Grant)**.
  </Step>

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

### Configure your Box app and gain approval

<Steps>
  <Step>
    Navigate to your new app's **Configuration** tab.
  </Step>

  <Step>
    In the **Application Scopes** area, select the following scopes:

    * Manage users
    * Manage groups
    * Manage enterprise properties
    * Grant read resource
  </Step>

  <Step>
    In the **Application Access** area, select **App + Enterprise Access**.
  </Step>

  <Step>
    Save your changes.
  </Step>

  <Step>
    Submit your new custom app for approval by a Box Admin. Learn more about this process in the [Box developer documentation](https://developer.box.com/guides/authorization/custom-app-approval/).
  </Step>
</Steps>

### Look up your new app's credentials

<Steps>
  <Step>
    Navigate to your new app's **Configuration** tab and scroll down to the **OAuth 2.0 Credentials** section of the page.
  </Step>

  <Step>
    Copy and carefully save the Client ID.
  </Step>

  <Step>
    Navigate to the app's **General Settings** page.
  </Step>

  <Step>
    Copy and carefully save the Enterprise ID.
  </Step>
</Steps>

### Add the new app to your Box instance

<Steps>
  <Step>
    Next, in the Box Admin Console, navigate to **Integrations** > **Platform Apps Manager**.
  </Step>

  <Step>
    Click **Platform Apps Manager**.
  </Step>

  <Step>
    Click the plus sign to add a platform app to your Box instance, then enter the client ID of your new app and click **Next**.
  </Step>

  <Step>
    Review the app's information and click **Authorize**.
  </Step>
</Steps>

### Generate a client secret

<Steps>
  <Step>
    Return to the Box Developer Console and navigate to your new app's **Configuration** tab.
  </Step>

  <Step>
    In the **App Access Level** area, select **App + Enterprise Access**.
  </Step>

  <Step>
    Scroll down to the **OAuth 2.0 Credentials** section of the page and click **Fetch Client Secret**.
  </Step>

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

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

## Configure the Box connector

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

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of Box 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 **Box** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Box 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>
        Enter the client ID and client secret into the **Client ID** and **Client secret** fields.
      </Step>

      <Step>
        Enter the enterprise ID into the **Enterprise ID** field.
      </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 Box connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Box 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-adobe): Access the source code, report issues, or contribute to the project.

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

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-box-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-box-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # Box credentials
      BATON_BOX_CLIENT_ID: <Client ID used to authenticate to the Box API>
      BATON_BOX_CLIENT_SECRET: <Client secret used to authenticate to the Box API>
      BATON_ENTERPRISE_ID: <ID of your Box app>
    ```

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

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