Set up a Twingate connector

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

This is an updated and improved version of the Twingate connector! If you’re setting up Twingate with C1 for the first time, you’re in the right place.

Capabilities

Resource	Sync	Provision
Accounts
Groups
Roles

Gather Twingate credentials

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

A user with the Admin role in Twingate must perform this task.

Generate a new API key

1. Log into Twingate as an Admin user and click Settings.

2. Click API.

3. Click Generate Token. Give the API token a label, such as C1.

4. Select the appropriate permission level for the API key:

   • Read only to run access reviews on your Twingate users.
   • Read & Write to provision group membership via C1 and run access reviews.
5. Click Generate. (Setting the Allowed Range is not required.)

6. The new API key is generated for you. Click Copy and save the key.

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

Configure the Twingate connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Twingate 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 Integrations > Connectors and click Add connector.

2. Search for Twingate and click Add.

3. Choose how to set up the new Twingate 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 C1)

   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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 you into the API key field.

8. In the Domain field, enter your Twingate domain.

   For example, if your Twingate instance address is sampledomain.twingate.com, enter sampledomain in the Domain 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 Twingate connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Twingate 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 Twingate connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Twingate 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 C1)

   • 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 C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 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 Twingate connector deployment:

Secrets configuration

# baton-twingate-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-twingate-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Twingate credentials
  BATON_API_KEY: <Twingate API key>
  BATON_DOMAIN: <Twingate domain, such as "sampledomain" if you access Twongate at "sampledomain.twingate.com">

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

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