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
Groups

Gather Broadcom SAC credentials

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

Important

A user with administrative privileges in the Broadcom SAC tenant must perform this task.

Create an API client and generate credentials

1. In the Broadcom SAC Admin portal, click Settings.

2. Navigate to Local Directory > API Clients.

3. Click New.

4. 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.

5. Click Save.

6. The new API client is generated, along with a client ID and client secret. Carefully copy and save these credentials.

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

Configure the Broadcom SAC connector

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

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Broadcom SAC and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. Find the Settings area of the page and click Edit.

8. Paste the Client ID and client secret into the Client ID and Client secret fields.

9. Enter your Broadcom SAC tenant address in the Tenant field.

10. Click Save.

11. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Broadcom SAC connector is now pulling access data into C1.

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: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Broadcom SAC connector

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Baton and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. In the Settings area of the page, click Edit.

8. Click Rotate to generate a new Client ID and Secret. Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Broadcom SAC connector deployment:

Secrets configuration

# 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

# 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: public.ecr.aws/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

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. 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.

Done. Your Broadcom SAC connector is now pulling access data into C1.