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.
This is an updated and improved version of the Twingate connector! If you’re setting up Twingate with ConductorOne for the first time, you’re in the right place.
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Twingate credentials generated by following the instructions above
Cloud-hosted
Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.
1
In ConductorOne, navigate to Admin > 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 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.
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 ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
In ConductorOne, navigate to 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 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.
# baton-twingate-secrets.yamlapiVersion: v1kind: Secretmetadata: name: baton-twingate-secretstype: OpaquestringData: # ConductorOne credentials BATON_CLIENT_ID: <ConductorOne client ID> BATON_CLIENT_SECRET: <ConductorOne 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 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.
Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
2
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 Twingate connector to. Twingate data should be found on the Entitlements and Accounts tabs.
That’s it! Your Twingate connector is now pulling access data into ConductorOne.
