Single Sign-On (SSO)

TeamViewer Tensor (Classic) with Single Sign-On gives IT more control over provisioning enterprise user accounts for TeamViewer Tensor (Classic) remote access and support. By limiting access to users with corporate emails only, TeamViewer Tensor (Classic) with SSO allows you to prevent unauthorized users from ever using your enterprise remote access platform.

• Centralize password control through your SSO identity service provider, so IT doesn’t have to manage passwords, reducing password reset requests.
• Automatically apply corporate password policies and identity authentication rules to every authorized TeamViewer Tensor (Classic) user.
• Efficiently offboard employees, without worrying about unauthorized backdoor access through TeamViewer.
• Improve the end-user experience by allowing employees to log in to TeamViewer Tensor (Classic) with the same SSO login credentials they’re already using for your corporate applications — no separate TeamViewer Tensor (Classic) login with another password to remember.

Requirements

To use TeamViewer Single Sign-On, you need

• a TeamViewer version 13.2.1080 or newer
• a SAML 2.0 compatible identity provider (IdP)*
• a TeamViewer account to access the Management Console and add domains
• access to the DNS management of your domain to verify the domain ownership
• a TeamViewer Tensor license.

* Currently, we only support Centrify, Okta, Azure, OneLogin, ADFS, and G Suite, but we are working on supporting more IdPs in the future. The above IdPs have been tested, and detailed steps to set up one of these IdP can be found in these documents and other linked pages about SSO and the respective IdPs. 

Note: If you use a different IdP, please use the technical information to set up your IdP manually.

Hint: When adding a domain for Single Sign-On, it is recommended to add the owning account to the exclusion list. The reason for this is a fallback scenario that you keep access to the domain configuration even if the IdP is not working. 

Example: The TeamViewer Account "admin@example.com" adds domain „example.com“ for Single Sign-On. After adding the domain, the email address "admin@example.com" should be added to the exclusion list. This is required to make changes to the SSO configuration, even when Single Sign-On doesn't work due to misconfiguration.

Hint2: When adding a single Sign-On domain, adding additional owners to the SSO domain is recommended since the SSO ownership is not inherited within your company. 

Example: After the TeamViewer Account "admin@example.com" adds domain „example.com“ for Single Sign-On, they add multiple company administrators (e.g. "admin2@example.com") as domain owners so that they can also manage the domain and its SSO settings.

Single Sign-On (SSO) is activated on a domain level for all TeamViewer accounts using an email address with this domain. Once activated, all users that sign into a corresponding TeamViewer account are redirected to the identity provider that has been configured for the domain. This step is required independent of which IdP is used.

For security reasons and to prevent abuse, it is required to verify the domain ownership before the feature is activated.

Add a new domain

To activate SSO, log in to Management Console select Company administration and then the Single Sign-On menu entry. Click on Add domain and enter the domain you want to activate SSO for.

You also need to provide your identity provider’s metadata. There are three options available to do so:

• via URL: enter your IdP metadata URL into the corresponding field
• via XML: select and upload your metadata XML
• Manual configuration: manually enter all necessary information. Please note that the public key must be a Base64 encoded string.

Identity Provider Setup

Each identity provider requires its own configuration, which is covered in dedicated knowledge base articles:

• Active Directory Federation Services (ADFS)
• Azure Active Directory
• Centrify
• G Suite
• Okta
• OneLogin

Required SAML Response Claims:

• http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier

This should be mapped to a unique user identifier within the scope of the IdP (and, therefore, within the scope of the corresponding company).

For example, this can be the Active Directory Object GUID for ADFS or the email address for Okta

• http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress

This attribute should be mapped to the email address of the user that wants to sign in. The email address needs to be the same as configured for the TeamViewer account. The mapping/comparison is done in a case-insensitive way.

• http://sso.teamviewer.com/saml/claims/customeridentifier

This attribute should return a customer-specific identifier. The attribute must be named “customeridentifier.”

TeamViewer requires a customer identifier as a custom claim in the SAML response for the initial configuration of Single Sign-On accounts.

TeamViewer does not store the customer identifier. Changing it later will break Single Sign-On, and a new setup will be necessary.

Any random string can be used as a customer identifier.

Signature & Encryption Certificate (Public Key)

The public key of the certificate that is used to sign SAML requests and for the encryption of SAML responses can be obtained by executing the following PowerShell command:

"-----BEGIN PUBLIC KEY-----`n" + ` ((Select-Xml ` -Content ((Invoke-WebRequest ` https://sso.teamviewer.com/saml/metadata.xml).Content) ` -xpath "//*[local-name()='X509Certificate']").Node[0].'#text') + ` "`n-----END PUBLIC KEY-----" ` | Out-File -FilePath "sso.teamviewer.com - saml.cer" -Encoding ascii

The command downloads the metadata extracts the public key, and writes it to a file.