Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Torq credentials

Each setup method requires you to pass in credentials generated in Torq. Gather these credentials before you move on.

A user with the ability to make an API key in Torq must perform this task.

Generate a Torq API key

1. In Torq, click your username and select API Keys.

2. Click Create API key.

3. Give the new API key a name, such as “ConductorOne integration”.

4. Click Create.

5. Carefully and copy and save the key’s client ID and client secret.

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

Set up a Torq cloud-hosted connector

To complete this task, you’ll need:

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

1. In ConductorOne, click Connectors > Add connector.

2. Search for Torq and click Add.

3. Choose how to set up the new Torq 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 client ID into the Client ID field.

8. Paste the client secret into the Client secret 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 Torq connector is now pulling access data into ConductorOne.

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

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

Set up a Torq self-hosted connector

To complete this task, you’ll need:

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

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

2. Search for Baton and click Add.

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

Secrets configuration

# baton-torq-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-torq-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Torq credentials
  BATON_TORQ_CLIENT_ID: <Torq client ID>
  BATON_TORQ_CLIENT_SECRET: <Torq client secret>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-torq.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-torq
  labels:
    app: baton-torq
spec:
  selector:
    matchLabels:
      app: baton-torq
  template:
    metadata:
      labels:
        app: baton-torq
        baton: true
        baton-app: torq
    spec:
      containers:
      - name: baton-torq
        image: ghcr.io/conductorone/baton-torq:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-torq-secrets

Step 3: Deploy the connector

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

   kubectl create namespace baton-torq
   

2. Apply the secret configuration:

   kubectl -n baton-torq apply -f baton-torq-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-torq apply -f baton-torq.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-torq}
   

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

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