Set up a Celigo connector

C1 provides identity governance and just-in-time provisioning for Celigo. Integrate your Celigo instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts
Integrations
Roles

Gather Celigo credentials

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

A user with the Account owner or Administrator role in Celigo must perform this task.

Generate a Celigo API token

1. In Celigo, navigate to Resources > API tokens.

2. Click Create API token.

3. Give the new API token a name, such as “C1 integration”.

4. In the Auto purge token field, select a lifetime for the token.

5. Set the token’s scope to Full access.

6. Click Save & close.

7. The new token is shown on the API tokens page. Click Show token to view the full token value.

8. Carefully and copy and save the new API token.

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

Configure the Celigo connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Celigo 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 Celigo 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. Select your Celigo region (United States or European Union).

9. Paste the API token you generated in Step 1 into the Access token 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 Celigo connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Celigo 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 Celigo 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 Celigo connector deployment:

Secrets configuration

# baton-celigo-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-celigo-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Celigo credentials
  BATON_CELIGO_ACCESS_TOKEN: <API access token generated for this integration>
  BATON_REGION: <Your Celigo region (default "us")>

  # 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-celigo.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-celigo
  labels:
    app: baton-celigo
spec:
  selector:
    matchLabels:
      app: baton-celigo
  template:
    metadata:
      labels:
        app: baton-celigo
        baton: true
        baton-app: celigo
    spec:
      containers:
      - name: baton-celigo
        image: public.ecr.aws/conductorone/baton-celigo:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-celigo
        envFrom:
        - secretRef:
            name: baton-celigo-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 Celigo connector to. Celigo data should be found on the Entitlements and Accounts tabs.

Done. Your Celigo connector is now pulling access data into C1.