Inside DigitalOcean’s SOX Compliance Playbook

ConductorOne docs

Set up a Twingate connector

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

Capabilities

ResourceSyncProvision
Accounts✅
Groups✅✅ (locally created groups only)
Roles✅

Available hosting methods

Choose the hosting method that best suits your needs:

MethodAvailabilityNotes
Cloud hosted✅A built-in, no-code connector hosted by ConductorOne.
Self-hostedA connector hosted and run in your own environment.

Gather Twingate credentials

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

  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 ConductorOne 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.

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

Set up a Twingate cloud-hosted connector

To complete this task, you’ll need:

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

  1. In ConductorOne, click Connectors > 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 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 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.

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

A user with the Connector Administrator or Super Administrator role in ConductorOne and Admin role in Twingate must perform this task.

Step 1: 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 ConductorOne.

  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 ConductorOne 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.

Step 2: Add your Twingate credentials to ConductorOne

  1. In ConductorOne, navigate to the Twingate connector by either:

    • Clicking the Set up connector link in the email you received about configuring the connector.

    • Navigate to Connectors > Twingate (if there is more than one Twingate listed, click the one with your name listed as owner and the status Not connected).

  2. Find the Settings area of the page and click Edit.

  3. Click Save.

  4. 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 Twingate connector is now pulling access data into ConductorOne.

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

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