Integrations

TeamViewer

TeamViewer enables remote control of your devices, enhancing your organization's remote management and support capabilities. This integration brings the following features to the 1E Platform:

  • An authentication process that handles API key usage; otherwise, manual authentication with TeamViewer is required.

  • The ability to create TeamViewer sessions for your devices.

  • Ensuring the end-user device has the TeamViewer client installed and configured for the session.

To take advantage of the TeamViewer integration note the following:

  • To enable this feature in your organization, you will need a TeamViewer Client ID and Client Secret.

  • You need to be an Enterprise or Enterprise Plus customer to utilize the TeamViewer DEX Pack included with the Platform.

Role-Based Access Control (RBAC) requirements

The 1E Platform supports a granular and flexible role-based access control system that allows you to control the actions that can be performed by users.

The 1E Platform includes a Remote Support system role with permissions restricted to installing TeamViewer, initiating sessions, and managing only the groups and devices assigned to them. This is a system role and cannot be delegated. Administrators must specifically assign this role to specific Management Groups or users. The restriction on delegation ensures that only Full Administrators can assign this role.

Refer to Roles and Roles and Securables.

TeamViewer DEX Pack

The DEX Pack used for the TeamViewer integration is included with the 1E Platform and is required by the following features:

  • To check if the TeamViewer full client is installed on Windows systems.

  • To initiate a TeamViewer remote session using the Session ID through TeamViewer Quick Support.

A full breakdown of the TeamViewer instructions is available on the 1E Exchange.

Enabling TeamViewer

To enable the TeamViewer integration, follow these steps:

  1. Navigate to Settings > Integrations > TeamViewer.

  2. Select the toggle to enable the feature. Once enabled, you will have the option to use TeamViewer to connect to a device.

  3. Enter your existing TeamViewer Client ID and Client Secret, and click Save.

    If you do not already have an existing Client ID and Client Secret you will need to log in to your TeamViewer account and create a PKCE application for the integration. Refer to TeamViewer PKCE app.

  4. When you click TeamViewer connect, you will connect through to that device using a browser-based remote session.

    If TeamViewer is not installed on the target device, then TeamViewer QuickSupport will be used. TeamViewer QuickSupport is a small module that does not require installation or administrator rights.

TeamViewer PKCE app

Follow these steps to create a PKCE application for your TeamViewer integration.

  1. Log into your TeamViewer account.

  2. Go to Settings > Apps & Tokens.

  3. Click Profile settings.

  4. You should see a list of Apps & Tokens, although it might be empty in your account.

  5. Click Create app or token > Create App.

  6. On the displayed form, fill in the Name, Description, and Redirect URI fields. The redirect will reflect your environment and be similar to this example:

    https://CustomerName.UKSouth.cloud.1e.com:443/Consumer/TeamViewerIntegration/TeamViewerRedirect

  7. For the application to function, you need to assign the following App permissions to it:

    • Session management: Select view own sessions, view all sessions, create sessions, edit own sessions.

    • User management: Select view users.

  8. Click Save.

You can now take the Client ID and Client Secret and use them for your deployment configuration.

Audit logs

When a remote session is initiated, the action is logged on both the 1E Platform and in TeamViewer. The Audit Information Log includes timestamps, user activity, and status of a session:

  • Who initiated the session.

  • The time a session was started.

  • On which device was the session created.

Refer to Monitoring.