Set up a Temporal Cloud connector

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

Capabilities

Resource	Sync	Provision
Accounts
Namespaces
Account roles*
Service accounts

*The Account Owner and Finance Manager roles are synced but cannot be provisioned.

The Temporal Cloud connector supports automatic account provisioning and deprovisioning.

Gather Temporal Cloud credentials

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

A user with the ability to create API keys in Temporal Cloud must perform this task.

Create a Temporal Cloud API key

1. In Temporal Cloud, navigate to your profile page and click API Keys.

2. Click Create API Key.

3. Enter a name and description for the new API key and select an expiration date (90 days is the maximum allowed value).

4. Click Generate API Key.

5. Carefully copy and save the API key.

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

Configure the Temporal Cloud connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Temporal Cloud 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 Temporal Cloud 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 API key into the API key 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.

Done. Your Temporal Cloud connector is now pulling access data into C1.

Self-hosted

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

Secrets configuration

# baton-temporalcloud-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-temporalcloud-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Temporal Cloud credentials
  BATON_API_KEY: <Temporal Cloud API key>

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

Done. Your Temporal Cloud connector is now pulling access data into C1.