On-demand access with ConductorOne
ConductorOne is a security platform that allows you to manage access requests for your Tailscale entitlements.
ConductorOne can also be used with user & group provisioning to update group membership in Okta groups used in Tailscale ACLs, or assign the Tailscale application users in Okta.
You can connect multiple tailnets to ConductorOne simultaneously.
Before you begin this guide, you’ll need a tailnet and a ConductorOne account.
For information about creating a tailnet, see the Tailscale quickstart.
For information about creating a ConductorOne account, see ConductorOne.
See the full instructions in ConductorOne’s blog post for setting up an integration with Tailscale.
To use ConductorOne with Tailscale, you’ll need to:
- Generate a Tailscale API key from the keys page of the admin console.
- In ConductorOne, select the Tailscale integration and then click Add Connector.
- Choose the option to Create a new app.
- Set the Tailscale API key to the API key you generated.
- Set the Tailnet to your tailnet’s domain name. For example,
example.org.github, etc. You can find the name of your tailnet in the Settings page of the admin console.
ConductorOne will automatically identify all the users in the tailnet and parse existing access rules in Tailscale ACLs, including SSH access rules, as entitlements in ConductorOne. The application owner in ConductorOne can specify for each entitlement, such as group membership or another SSH access rule, whether to restrict access by time, and whether to use the default application grant policy.
Now a user can request access to a specific Tailscale entitlement through the Request access page of ConductorOne and through Slack.