Set up a TeamViewer connector

C1 provides identity governance for TeamViewer. Integrate your TeamViewer instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts
Roles
Groups	*	*

The TeamViewer connector supports automatic account provisioning and deprovisioning.

*Group syncing is opt-in. Enable it when you configure the connector.

Syncing user groups requires a TeamViewer Tensor license. On Business and Premium licenses, TeamViewer’s user group API returns a license_required error, so the connector cannot sync groups or manage group membership. The User groups feature is also absent from the TeamViewer Management Console on those licenses. See User groups and roles in TeamViewer’s documentation.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

Action name	Additional fields	Description
enable_user	user_id (string, required)	Enables a disabled TeamViewer user account
disable_user	user_id (string, required)	Disables an active TeamViewer user account

Gather TeamViewer credentials

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

A user who is able to access the TeamViewer Management Console must perform this task.

Generate an API token

1. In the TeamViewer Management Console, click your profile menu and select Edit Profile.

2. On the Apps tab, click Create Script Token.

3. Give the new API token a name, such as “C1”.

4. Set the relevant permissions:

   To give C1 sync (READ) access:

   • View account data - Required to sync user information
   • View email address - Required to sync user email addresses
   • View online state - Required for last login
   • View license - To see active state
   • View users - Required to sync users
   • Read user groups - Required to sync user groups (Tensor license only)

   To give C1 sync and provision (READ/WRITE) access:

   • View account data - Required to sync user information
   • View email address - Required to sync user email addresses
   • View online state - Required for last login
   • View license - To see active state
   • View users - Required to sync users
   • Read user groups - Required to sync user groups (Tensor license only)
   • Edit account properties - Required to update user properties (such as enabling/disabling accounts)
   • Create users - Required to provision accounts
   • Edit users - Required to update user properties and manage role assignments
   • Edit user groups - Required to manage group memberships (Tensor license only)
5. Click Save. Carefully copy and save the newly generated API token.

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

Configure the TeamViewer connector

To complete this task, you’ll need:

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

2. Search for TeamViewer and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

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

8. Enter your API token in the API token field.

9. Optional. If you want the connector to sync group information form TeamViewer, click to enable Sync groups.

10. Optional. If your TeamViewer account uses SSO, enter your SSO Customer ID in the SSO Customer ID field. When set, newly provisioned user accounts will be linked to SSO automatically.

11. Click Save.

12. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

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

Self-hosted

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

Contact C1’s support team to download the latest version of the connector.

Step 1: Set up a new TeamViewer connector

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Baton and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. In the Settings area of the page, click Edit.

8. 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 TeamViewer connector deployment:

Secrets configuration

# baton-teamviewer-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-teamviewer-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # TeamViewer credentials
  BATON_API_TOKEN: <TeamViewer API token>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

  # Optional: include if you want C1 to sync group information
  BATON_SYNC_GROUPS: true

  # Optional: include if your TeamViewer account uses SSO
  BATON_SSO_CUSTOMER_ID: <TeamViewer SSO Customer ID>

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

Deployment configuration

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

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