Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Celigo credentials

Each setup method 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 “ConductorOne 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.

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

Set up a Celigo cloud-hosted connector

To complete this task, you’ll need:

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

1. In ConductorOne, navigate to Admin > Connectors and click Add connector.

2. Search for Celigo and click Add.

3. Choose how to set up the new Celigo 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. Select your Celigo region (United States or European Union).

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

Set up a Celigo 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 Celigo and ConductorOne.

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

Set up a Celigo self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Celigo 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 Celigo connector

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

2. Search for Baton and click Add.

3. Choose how to set up the new Celigo 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 Celigo connector deployment:

Secrets configuration

# baton-celigo-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-celigo-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne 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 ConductorOne 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: ghcr.io/conductorone/baton-celigo:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-celigo-secrets

Step 3: Deploy the connector

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

   kubectl create namespace conductorone
   

2. Apply the secret configuration:

   kubectl -n conductorone apply -f baton-celigo-secrets.yaml
   

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-celigo.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n conductorone get pods
   

2. View the connector logs:

   kubectl -n conductorone logs -l app=baton-${baton-celigo}
   

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

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