Thycotic Secret Server Cloud Integration with AuthPoint

Deployment Overview

This document describes how to set up multi-factor authentication (MFA) for Thycotic® Secret Server Cloud with AuthPoint as an identity provider. Thycotic Secret Server Cloud must already be configured and deployed before you set up MFA with AuthPoint.

Thycotic Secret Server Cloud can be configured to support MFA in several modes. For this integration, we set up SAML with AuthPoint.

This integration was tested with Thycotic Secret Server Cloud v10.5.000010.

Thycotic Secret Server Cloud Authentication Data Flow with AuthPoint

AuthPoint communicates with various cloud-based services and service providers with the SAML protocol. This diagram shows the data flow of an MFA transaction for Thycotic Secret Server Cloud.

topology

Before You Begin

Before you begin these procedures, make sure that:

Configure Thycotic Secret Server Cloud

  1. Log in to WatchGuard Cloud.
  2. From the navigation menu, select Configure > AuthPoint. If you have a Service Provider account, you must select an account from Account Manager.
  3. Select Resources.
  4. Click Certificate.

  1. Next to AuthPoint certificate you will associate with your resource, click and select Download Metadata. We recommend that you choose the certificate with the latest expiration date. If you do not have a certificate, or if all of your certificates have expired, click Add Certificate and use the newly created certificate.

    The AuthPoint metadata provides your resource, in this case Thycotic, with information necessary to identify AuthPoint as a trusted identity provider.

  1. Log in to your Thycotic Secret Server Cloud as an administrator.
  2. Select Admin.
  3. Select Configuration.

navigate to configuration

  1. Select the SAML tab.
  2. In the SAML General Settings section, click Edit,
  3. Select the SAML Enabled check box to enable SAML. Click Save.

SAML General Settings

  1. A self signed certificate is required. Go to https://github.com/thycotic/extrabits/blob/master/Generate-Cert.ps1. Copy the code and replace the variables in the script as directed, then run the script in Powershell as an administrator.
  2. In the SAML Service Provider Settings section, click Edit.
  3. In the Name text box, type a name. In our example, we type SecretServerServiceProvider.
  4. Click Select Certificate.
    The Upload Certificate dialog box opens.
  5. Click Upload Certificate and select the certificate you generated.
  6. In the Password text box, type the password you set in the Powershell script. Click OK.
  7. Click Save.
  8. Click Download Service Provider Metadata(XML) to save the metadata file.

SAML Service Provider Settings

  1. In Identity Providers section, click Create New Identity Provider.
  2. Click Import IDP from XML Metadata to import AuthPoint metadata file. The configuration is applied automatically.

Identity Providers

Configure AuthPoint

Before AuthPoint can receive authentication requests from Thycotic Secret Server Cloud, you must add a SAML resource in AuthPoint. You must also create an authentication policy for the Thycotic Secret Server Cloud resource to determine which users can authenticate and log in to Thycotic Secret Server Cloud and which authentication methods they can use (Push, QR code, and OTP).

Add a SAML Resource in AuthPoint

From the AuthPoint management UI:

  1. From the navigation menu, select Resources. Click Add Resource.
    The Add Resource page opens.

  1. From the Type drop-down list, select SAML.
    Additional fields appear.

  1. On the SAML page, in the Name text box, type a name for this resource.
  2. From the Application Type drop-down list, select Others.
  3. In the Service Provider Entity ID text box, type the name of the SAML Service Provider you specified in Thycotic. This value is copied from the Thycotic metadata file.
  4. In the Assertion Consumer Service text box, type https://<your instance name>/SAML/AssertionConsumerService.aspx. This value is copied from the Thycotic metadata file.
  5. From the User ID drop-down list, select Email or User Name.
  6. In the Logout URL text box, type https://<your instance name>/SAML/SLOService.aspx. This value is copied from the Thycotic metadata file.
  7. From the AuthPoint Certificate drop-down list, select the AuthPoint certificate to associate with your resource. This must be the same certificate that you downloaded the metadata for in the previous section.
  8. Click Save.

Add a Group in AuthPoint

You must have at least one user group in AuthPoint to configure MFA. If you already have a group, you do not have to add another group.

To add a WatchGuard Cloud-hosted group to the WatchGuard Cloud Directory:

  1. Go to Configure > Directories and Domain Services.
  2. Click the WatchGuard Cloud Directory domain name. If you have not yet added the WatchGuard Cloud Directory, click Add Authentication Domain and select the WatchGuard Cloud Directory.
    The New Group page appears.

Screenshot that shows the Directories and Domain Services page.

  1. In the Groups tab, click Add Group.
  2. In the Group Name text box, type a descriptive name for the group.
  3. (Optional) In the Description text box, type a description of the group.

Screen shot of the Add Group page.

  1. Click Save.
    Your group is added to the WatchGuard Cloud Directory and to AuthPoint.

Add an Authentication Policy to AuthPoint

Authentication policies specify which resources users can authenticate to and which authentication methods they can use (Push, QR code, and OTP).

You must have at least one authentication policy in AuthPoint that includes the Thycotic Secret Server Cloud resource. If you already have authentication policies, you do not have to create a new authentication policy. You can add this resource to your existing authentication policies.

Users that do not have an authentication policy for a specific resource cannot authenticate to log in to that resource.

To configure an authentication policy:

  1. From the navigation menu, select Authentication Policies.
  2. Click Add Policy.

Screenshot of the Add Policy button on the Authentication Policies page.

  1. Type a name for this policy.
  2. From the Select the Authentication Options drop-down list, select Authentication Options and select which authentication options users can choose from when they authenticate.

    For SAML resources, if you select more than one authentication option, users must select one of the available options when they authenticate. For example, if you select OTP and Push, users can choose to type their OTP or approve a push to authenticate. You cannot require that they do both.

  1. Select which groups this policy applies to. You can select more than one group. To configure this policy to apply to all groups, select All Groups.
  2. Select the resource that you created in the previous section. If you want this policy to apply to additional resources, select each resource this policy applies to. To configure this policy to apply to all resources, select All Resources.

Screenshot of the Add Policy page with the groups and resources selected

  1. (Optional) If you have configured policy objects such as a Network Location, select which policy objects apply to this policy. When you add a policy object to a policy, the policy only applies to user authentications that are the same as the conditions of the policy objects. For example, if you add a Network Location to a policy, the policy only applies to user authentications that come from that Network Location. Users who only have a policy that includes a Network Location do not get access to the resource when they authenticate outside of that Network Location (because they do not have a policy that applies, not because authentication is denied).

    If you configure policy objects, we recommend that you create a second policy for the same groups and resources without the policy objects. The policy with the policy objects should have a higher priority.

Screenshot of the Policy Objects drop-down list.

  1. Click Save.
    Your policy is created and added to the end of the policy list.

    When you create a new policy, we recommend that you review the order of your policies. AuthPoint always adds new policies to the end of the policy list.

Screenshot of the Save button on the Add Policy page.

Add Users to AuthPoint

Before you assign users to a group, you must add the users to AuthPoint. There are two ways to add AuthPoint user accounts:

  • Sync users from an external user database
  • Add WatchGuard Cloud-hosted AuthPoint users

Each user must be a member of a group. You must add at least one group before you can add users to AuthPoint.

To import users from Active Directory, Microsoft Entra ID, or an LDAP database, you must add an external identity in the AuthPoint management UI. External identities connect to user databases to get user account information and validate passwords.

  • To sync users from Active Directory or an LDAP database, you must add an LDAP external identity
  • To sync users from Microsoft Entra ID, you must add a Microsoft Entra ID external identity

When you sync users from an external user database, you can sync any number of users and they are all added to AuthPoint at one time. Users synced from an external user database use the password defined for their user account as their AuthPoint password.

To learn how to sync users, go to Sync Users from Active Directory or LDAP and Sync Users from Azure Active Directory.

You create WatchGuard Cloud-hosted users and groups from the WatchGuard Cloud Directory in WatchGuard Cloud. Directories and Domain Services is where you add shared authentication domains for WatchGuard Cloud devices and services, such as AuthPoint.

Users that you add to the WatchGuard Cloud Directory are automatically added to AuthPoint as well.

You add local AuthPoint users form Directories and Domain Services. You manage the users in AuthPoint on the Users page.

When you add WatchGuard Cloud-hosted AuthPoint users, you choose whether the user is an MFA user or a non-MFA user.

  • MFA users are user accounts that will use AuthPoint multi-factor authentication to authenticate. This is not related to the AuthPoint Multi-Factor Authentication license type.
  • Non-MFA users are users that will only ever authenticate with a password, such as a service account user. Non-MFA users do not consume an AuthPoint user license and cannot authenticate to resources that require MFA. They can only authenticate to protected resources if the non-MFA user account has a password only authentication policy for that resource.

After you add a user, you can edit the user account if you need to change their account type. When you change a user account from MFA to non-MFA, AuthPoint deletes the tokens and password vault (if applicable) that belong to the user. This action cannot be undone.

Unlike users synced from an external user database, WatchGuard Cloud-hosted AuthPoint users define and manage their own AuthPoint password. When you add a WatchGuard Cloud-hosted user account, the user receives an email that prompts them to set their password.

To learn how to add WatchGuard Cloud-hosted AuthPoint user accounts to the WatchGuard Cloud Directory, go to Add Local Users to an Authentication Domain.

Test the Integration

To test MFA for Thycotic Secret Server Cloud, you can authenticate with a mobile token on your mobile device. You can choose any method (one-time password, QR code, or push).

In this example, we show the push authentication method (users receive a push notification in the mobile app that they must approve to authenticate).

  1. In a web browser, go to the Thycotic Secret Server Cloud URL.
  2. Type your email address or AuthPoint user name. Click Next.
  3. If required, in the Password text box, type your password.
  4. For the authentication method, select Push.
  5. Click Send.
  6. Approve the authentication request that is sent to your mobile device.
    You are logged in to Thycotic Secret Server Cloud.