Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Broadcom SAC credentials

Each setup method requires you to pass in credentials generated in Broadcom SAC. Gather these credentials before you move on.

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 “ConductorOne”) 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.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a Broadcom SAC cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Broadcom SAC credentials generated by following the instructions above

1. In ConductorOne, click Connectors > Add connector.

2. Search for Broadcom SAC and click Add.

3. 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 ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

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

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

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

9. Click Save.

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

That’s it! Your Broadcom SAC connector is now pulling access data into ConductorOne.

Set up a Broadcom SAC cloud-hosted connector using Terraform

As an alternative to the cloud-hosted integration process described above, you can use Terraform to configure the integration between Broadcom SAC and ConductorOne.

See the ConductorOne Broadcom SAC integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a Broadcom SAC self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Broadcom SAC credentials generated by following the instructions above

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Broadcom SAC connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. 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 ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

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

7. 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:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne 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: ghcr.io/conductorone/baton-broadcom-sac:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-broadcom-sac-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-broadcom-sac
   

2. Apply the secret configuration:

   kubectl -n baton-broadcom-sac apply -f baton-broadcom-sac-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-broadcom-sac apply -f baton-broadcom-sac.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-broadcom-sac}
   

3. Check that the connector data uploaded correctly. In ConductorOne, click Applications. 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.

That’s it! Your Broadcom SAC connector is now pulling access data into ConductorOne.