> ## 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 Broadcom SAC connector

> C1 provides identity governance for Broadcom SAC. Integrate your Broadcom SAC instance with C1 for unified visibility and governance over user access.

## Capabilities

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

## Gather Broadcom SAC credentials

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

<Warning>
  **Important**

  A user with administrative privileges in the Broadcom SAC tenant must perform this task.
</Warning>

### Create an API client and generate credentials

<Steps>
  <Step>
    In the Broadcom SAC Admin portal, click **Settings**.
  </Step>

  <Step>
    Navigate to **Local Directory** > **API Clients**.
  </Step>

  <Step>
    Click **New**.
  </Step>

  <Step>
    In the **New API Client** dialog, give the new API client a name (such as "C1") and enter a description, then check **Allow access to Secure Access Cloud management API**.
  </Step>

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

  <Step>
    The new API client is generated, along with a client ID and client secret. Carefully copy and save these credentials.
  </Step>
</Steps>

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

## Configure the Broadcom SAC connector

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

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

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

      <Step>
        Enter your Broadcom SAC tenant address in the **Tenant** 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 Broadcom SAC connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Broadcom SAC 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 Broadcom SAC 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 Broadcom SAC 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 Broadcom SAC connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-broadcom-sac-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-broadcom-sac-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # Broadcom SAC credentials
      BATON_SAC_CLIENT_ID: <Client ID for the API client>
      BATON_SAC_CLIENT_SECRET: <Client secret for the API client>
      BATON_TENANT: <Name of your Broadcom SAC tenant>
    ```

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

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