Capabilities

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

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Temporal Cloud credentials

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

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

Set up a Temporal Cloud cloud-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Temporal Cloud and click Add.

3. Choose how to set up the new Temporal Cloud 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 API key into the API key field.

8. Click Save.

9. 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 Temporal Cloud connector is now pulling access data into ConductorOne.

Set up a Temporal Cloud cloud-hosted connector using Terraform

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

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

Set up a Temporal Cloud self-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Baton and click Add.

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

Secrets configuration

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

  # 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-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: ghcr.io/conductorone/baton-temporalcloud:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-temporalcloud-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-temporalcloud-secrets.yaml
   

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-temporalcloud.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-temporalcloud}
   

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

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