Set up Sigma Computing connector

Capabilities

Resource	Sync	Provision
Account
Team

Additional functionality: Supports automatic account provisioning and deprovisioning

Grant and revoke Team Member. Team Admin is sync-only — Sigma’s API has no endpoint to grant or revoke team-admin status, so it can be reviewed but not provisioned through C1.

Gather Sigma Computing configuration information

Configuring the connector requires you to pass in information from Sigma Computing. Gather these configuration details before you move on. Here’s the information you’ll need:

Client ID
Client Secret
Domain

See the Sigma Computing docs for information on how to acquire credentials: View the documentation

Configure the Sigma Computing connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of Sigma Computing configuration information gathered by following the instructions above

Cloud-hosted
Self-hosted

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

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

Search for Sigma Computing and click Add.

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.

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

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

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

Find the Settings area of the page and click Edit.

Enter the configuration information from the previous section.

Click Save.

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

Done. Your Sigma Computing connector is now pulling access data into C1.

Follow these instructions to use the Sigma Computing 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

Contact C1’s support team to download the latest version of the connector.

Step 1: Set up a new Sigma Computing connector

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

Search for Baton and click Add.

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

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

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

In the Settings area of the page, click Edit.

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 Sigma Computing connector deployment:

Secrets configuration

# baton-sigmacomputing-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-sigmacomputing-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Sigma Computing config
  BATON_SIGMA_COMPUTING_CLIENT_ID: <Client ID for your Sigma Computing instance>
  BATON_SIGMA_COMPUTING_CLIENT_SECRET: <Client Secret for your Sigma Computing instance>
  BATON_SIGMA_COMPUTING_DOMAIN: <Domain of your Sigma instance (e.g. aws-api.sigmacomputing.com) See: https://help.sigmacomputing.com/reference/get-started-sigma-api#identify-your-api-request-url>

  # 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

# baton-sigmacomputing.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-sigmacomputing
  labels:
    app: baton-sigmacomputing
spec:
  selector:
    matchLabels:
      app: baton-sigmacomputing
  template:
    metadata:
      labels:
        app: baton-sigmacomputing
        baton: true
        baton-app: sigmacomputing
    spec:
      containers:
      - name: baton-sigmacomputing
        image: public.ecr.aws/conductorone/baton-sigmacomputing:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-sigmacomputing
        envFrom:
        - secretRef:
            name: baton-sigmacomputing-secrets

Step 3: Deploy the connector

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

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 sigmacomputing connector to. sigmacomputing data should be found on the Entitlements and Accounts tabs.

Done. Your Sigma Computing connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up Sigma Computing connector

Capabilities

Gather Sigma Computing configuration information

Configure the Sigma Computing connector

Resources

Step 1: Set up a new Sigma Computing connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather Sigma Computing configuration information

​Configure the Sigma Computing connector

​Resources

​Step 1: Set up a new Sigma Computing connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Sigma Computing configuration information

Configure the Sigma Computing connector

Resources

Step 1: Set up a new Sigma Computing connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector