AuthPoint Deployment Guide

You manage AuthPoint from WatchGuard Cloud. There are two types of WatchGuard Cloud account — Service Provider and Subscriber — each with a different view of WatchGuard Cloud.

To find out which type of WatchGuard Cloud account you have:

You can determine whether you have a Service Provider account or a Subscriber account based on the appearance of the WatchGuard Cloud UI and the navigation menu.

If you see an Account Manager menu and the navigation menu includes an Inventory menu option, then you have a Service Provider account.

If you see a dashboard similar to this and no Account Manager menu, then you have a Subscriber account.

If you have a Service Provider account, before you can set up AuthPoint, you must go to the Inventory page and allocate AuthPoint user licenses to your account. For more information, see Allocate Users to Your Account.

You configure and manage AuthPoint from the Configure Services section of WatchGuard Cloud.

To navigate to the AuthPoint management UI in WatchGuard Cloud:

1. Log in to WatchGuard Cloud at http://cloud.watchguard.com/.
   The WatchGuard Cloud Dashboard page is shown.
2. From the navigation menu, select Configure > AuthPoint. If you have a Service Provider account, you must select an account from Account Manager.
   The AuthPoint Summary page opens.

The AuthPoint Gateway is an application that you install on your network to synchronize user account information between your LDAP or Active Directory server and AuthPoint.

The Gateway functions as a RADIUS server and is required for RADIUS authentication and for LDAP synced users to authenticate with SAML resources. You must install the Gateway so that AuthPoint can communicate with your RADIUS clients and LDAP databases.

You can configure more than one Gateway on a network. For each primary Gateway that you configure, you can configure up to five secondary Gateways.

Primary Gateway

The primary Gateway synchronizes your LDAP users and enables RADIUS authentication and LDAP user authentication. This Gateway is the primary point of communication between AuthPoint and your RADIUS clients, the AuthPoint agent for ADFS, and your Active Directory or LDAP database.

Secondary Gateway

You can configure secondary Gateways as a failover for LDAP user authentication. When your primary Gateway is not available, AuthPoint automatically sends LDAP user authentications through the secondary Gateway until the primary Gateway becomes available again.

You can also use secondary Gateways as a backup RADIUS server. The only limitation is that the third-party software or device that sends authentication requests to the Gateway must support the use of additional RADIUS servers.

You cannot use secondary Gateways for load balancing or LDAP user synchronization.

Before you install the Gateway, you must configure it in the AuthPoint management UI.

To configure and install the AuthPoint Gateway:

1. From the AuthPoint navigation menu, select Gateway.
2. Click Add Gateway.

3. In the Name text box, type a descriptive name for the Gateway.

4. Click Save.
5. On the Gateway page, at the bottom of the tile for your Gateway, click Registration Key.

6. In the Gateway Registration Key dialog box, copy the registration key. You need this value to install the Gateway.

   The Gateway registration key is a one-time use key. If the installation of the Gateway fails, you must generate a new key to use for the installation.

7. From the navigation menu, select Downloads.
8. In the Gateway Installer section, click Download Installer.

9. Run the downloaded Gateway installer anywhere on your network that has Internet access and that can connect to your RADIUS clients and LDAP servers.
   WatchGuard AuthPoint Gateway Setup dialog box opens.
10. In the Gateway Registration Key text box, type or paste the Gateway registration key you copied from AuthPoint.
11. Click Install.

12. Click Finish.

13. In the AuthPoint management UI, on the Gateway page, check the circular icon next to your Gateway name. A green icon indicates that the Gateway is successfully installed and can communicate with AuthPoint.

    If the installation of the Gateway fails, you must generate a new registration key to use for the installation. For more information, see Gateway Registration Key.

For detailed steps to configure one or more secondary Gateways, see Configure and Install Secondary Gateways.

External identities connect to user databases to get user account information and validate passwords. To sync users from an external user database, you must add an external identity.

In this example, we show the steps to sync users from Active Directory or a Lightweight Directory Access Protocol (LDAP) database. To learn how to create an external identity to sync users from Azure Active Directory, see Sync Users from Azure Active Directory.

To add an external identity, from the AuthPoint management UI:

1. Select External Identities.

2. Click Add External Identity.
   The Add External Identity page opens.

3. From the Type drop-down list, select LDAP Configuration.
   Additional fields are shown.
4. In the Name text box, type a descriptive name for the external identity.
5. In the LDAP Search Base text box, type your LDAP database. In this example, the domain is example.com so we type dc=example,dc=com. Tip! The standard format for the search base setting is: ou=<name of organizational unit>,dc=<first part of the distinguished server name>,dc=<any part of the distinguished server name that appears after the dot>.

   For more information about LDAP syntax and how to use a search base to limit the directories on the authentication server where the external identity can search for users, see Find Your Active Directory Search Base.

6. In the System Account and Passphrase text boxes, type the credentials for a user that has permissions to perform LDAP searches and binds. If this user is not in the default Users folder, select the toggle and type the full distinguished name of the user. You can specify a passphrase up to 255 characters in length.Tip! The standard format for the distinguished name of a user is: cn=<name of user>,ou=<name of organizational unit>,dc=<first part of the distinguished server name>,dc=<any part of the distinguished server name that appears after the dot>.

   In this example, we have a user named administrator that is in an OU called AuthPoint (not the default Users folder). So, we must select the toggle and type the distinguished name of our user as CN=administrator,OU=AuthPoint,DC=example,DC=com. If this user was in the default Users folder, we would just type the user name administrator.

   If the user is in the Users folder and the user name is different than the account name (sAMAccountName), you must type the account name in the System Account text box.

7. From the Synchronization Interval drop-down list, specify how often you want to synchronize the LDAP database. If you select Every 24 hours, you must also specify what time the synchronization starts each day.

   For LDAP external identities that you configure to sync once every 24 hours, the Synchronization Interval time uses the time zone of the LDAP server.

8. For Type, select whether this is an Active Directory server or a different type of LDAP database. For other databases, you must specify each attribute value. You do not have to do this for Active Directory because the attribute values are known.
9. In the Domain text box, type your LDAP domain name.
10. If this not an Active Directory server, type a value for each attribute.

    If your Active Directory users use ADFS, you must keep the default sAMAccountName value for the attribute related to user login.

11. In the Server Address text box, type the IP address of your LDAP server.

    If your Active Directory instance does not use LDAPS Secure Lightweight Directory Access Protocol, you must disable the LDAPS toggle for the external identity. When you do this, the default port changes from 636 to 389.

12. In the Server Port text box, type the port for your server.

13. (Optional) To add a redundant address for your external identity, click Add Redundant Address and type a different address and port for the same LDAP database.
14. Click Save.

Next, you must add your external identity to the configuration for your AuthPoint Gateway. After you do that, you can test the connection to your LDAP database.

1. From the navigation menu, select Gateway.
2. Click the Name of your Gateway.
3. In the LDAP section, in the Select an LDAP external identity list, select your LDAP or Active Directory server.

4. Click Save.
5. From the navigation menu, select External Identities.
6. Next to the external identity you added for your LDAP database, click and select Check Connection.

AuthPoint is now connected to your LDAP database. You can create a query to sync users, but before you do that we recommend that you add resources for all of the applications and services that you want to require authentication for.

In AuthPoint, resources are the applications that you protect with AuthPoint. When you add a resource, you provide the information required for AuthPoint to connect to that resource.

When you add and configure a resource in AuthPoint, authentication is required to log in to that resource. For each resource, users must be a member of a group that has an authentication policy that includes that resource to authenticate and log in.

Users who are not a member of groups that have an authentication policy for a specific resource cannot authenticate to log in to that resource.

See AuthPoint Integration Guides for more information about how to set up authentication with specific third-party services and applications.

To add Firebox resources

To enable AuthPoint as an authentication server on a Firebox that runs Fireware 12.7 or higher, configure a Firebox resource in AuthPoint. This makes it easier to configure AuthPoint MFA for:

• Mobile VPN with SSL
• Mobile VPN with IKEv2
• Firebox Web UI
• Firebox Authentication Portal

When you configure a Firebox resource to add MFA to a Firebox, AuthPoint receives the IP address of the end user, so network location policy objects apply when a user authenticates with a VPN client.

You do not have to add a Firebox resource to your Gateway configuration, even if the Firebox resource has MS-CHAPv2 enabled. In this scenario, the Firebox validates the user password with NPS and AuthPoint authenticates the user with MFA.

Before you configure a Firebox resource, make sure that you have registered and connected the device to WatchGuard Cloud as a locally-managed Firebox. For cloud-managed Fireboxes and Fireboxes that run Fireware v12.6.x or lower, we recommend that you configure a RADIUS client resource for the Firebox.

For detailed instructions to register and connect your Firebox to WatchGuard Cloud, see Add a Locally-Managed Firebox to WatchGuard Cloud.

To add a Firebox resource:

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

2. Click Add Resource.
   
   The Add Resource page opens.

3. From the Type drop-down list, select Firebox.

4. In the Name text box, type a descriptive name for the resource.
5. From the Firebox drop-down list, select the Firebox or FireCluster that you want to connect to AuthPoint. This list only shows locally-managed Fireboxes and FireClusters that you have added to WatchGuard Cloud.

6. To configure the Firebox resource to accept MS-CHAPv2 authentication requests, click the Enable MS-CHAPv2 toggle.
   
   Additional text boxes appear.

   You do not have to enable MS-CHAPv2 if the IKEv2 VPN client is only used by local AuthPoint users.

7. In the NPS RADIUS Server Trusted IP or FQDN text box, type the IP address or fully qualified domain name (FQDN) of the NPS RADIUS server.
8. In the Port text box, type the port that NPS uses for communication. The default port is 1812.
9. In the Timeout In Seconds text box, type a value in seconds. The timeout value is the amount of time before a push authentication expires.
10. In the Shared Secret text box, type the shared secret key that NPS and the Firebox use to communicate.

11. Click Save.

After you add the Firebox resource in AuthPoint, the AuthPoint authentication server on your Firebox is enabled. To add MFA, you must configure the Firebox to use the AuthPoint authentication server for the features you want:

• Mobile VPN with SSL — In Fireware, configure AuthPoint as the primary authentication server for your Mobile VPN with SSL configuration. For detailed steps, see Firebox Mobile VPN with SSL Integration with AuthPoint.

  If you add the AuthPoint authentication server to your Mobile VPN with SSL configuration, users must download and use the WatchGuard Mobile VPN with SSL client v12.7 or higher or the OpenVPN SSL client.

• Mobile VPN with IKEv2— In Fireware, configure AuthPoint as the primary authentication server for your Mobile VPN with IKEv2 configuration. For detailed steps, see Firebox Mobile VPN with IKEv2 Integration with AuthPoint for Active Directory Users or Firebox Mobile VPN with IKEv2 Integration with AuthPoint for Azure Active Directory Users.
• Firebox Authentication Portal — In Fireware, specify AuthPoint as the authentication server for users and groups. For detailed steps, see Firebox Authentication with AuthPoint.
• Fireware Web UI — In Fireware, select System > Users and Roles and add Device Management users with AuthPoint as the authentication server. For more information, see Manage Users and Roles on Your Firebox

To add RADIUS client resources

RADIUS client resources represent a device or application that sends RADIUS packets to the AuthPoint Gateway. These are commonly used to authenticate users for firewalls and VPNs.

To configure MFA for a Firebox that runs Fireware v12.7 or higher and has been added to WatchGuard Cloud as a locally-managed Firebox, we recommend that you add a Firebox resource.

RADIUS client resources must be linked to the AuthPoint Gateway and you must choose a shared secret key so that the RADIUS server (AuthPoint Gateway) and the RADIUS client can communicate.

To add RADIUS client resources:

1. From the navigation menu, select Resources.
2. Click Add Resource.
   The Add Resource page opens.
3. From the Type drop-down list, select RADIUS Client.
4. In the Name text box, type a descriptive name for the resource.
5. In the RADIUS client trusted IP or FQDN text box, type the IP address that your RADIUS client uses to send RADIUS packets to the AuthPoint Gateway. This must be a private IP address. For Fireboxes, this is usually the Trusted IP address of your Firebox.
6. From the Value sent for RADIUS attribute 11 drop-down list, specify what is sent for the attribute 11 (Filter-ID) value in RADIUS responses. You can choose to send the user's AuthPoint group or the user's Active Directory groups.

   To specify a Filter-ID value, you must install version 5 or higher of the AuthPoint Gateway.

7. In the Shared Secret text box, type a password that the RADIUS server (AuthPoint Gateway) and the RADIUS client will use to communicate.
8. To configure the RADIUS client resource to accept MS-CHAPv2 authentication requests, enable the Enable MS-CHAPv2 toggle. You might do this if you want to configure AuthPoint MFA for IKEv2.
   Additional fields appear.

   To enable MS-CHAPv2, you must install version 5.3.1 or higher of the AuthPoint Gateway.

9. In the NPS RADIUS Server trusted IP or FQDN text box, type the IP address or FQDN of the NPS RADIUS server.
10. In the Port text box, type the port number for the Gateway (RADIUS server) to use to communicate with NPS. The default port is 1812.

    If NPS and the Gateway are installed on the same server, the port that the Gateway uses to communicate with NPS must be different than the port that the Gateway uses to communicate with the RADIUS client.

11. In the Timeout in Seconds text box, type a value in seconds. The timeout value is the amount of time before a push authentication expires.
12. Click Save.

Next, you must add your RADIUS client resource to the configuration for your AuthPoint Gateway. This is necessary for the RADIUS client to communicate with the RADIUS server (Gateway) and with AuthPoint.

To connect your RADIUS client resource to the Gateway:

1. From the navigation menu, select Gateway.
2. Click the Name of your Gateway.
3. In the RADIUS section, in the Port text box, type the port number for the RADIUS client to use to communicate with the Gateway (RADIUS server). The default Gateway ports are 1812 and 1645.

   If you already have a RADIUS server installed that uses port 1812 or 1645, you must use a different port for the AuthPoint Gateway.

4. From the Select a RADIUS resource list, select your RADIUS client resource or resources.

5. Click Save.

You have successfully added a RADIUS client resource and connected it with your Gateway. The last step is to configure your RADIUS client for authentication. Refer to the AuthPoint Integration Guides for the steps to configure specific RADIUS client resources.

To add SAML resources

SAML resources connect AuthPoint with the provider of a third-party service that users connect to (third-party service provider), such as Microsoft or Salesforce. Add SAML resources and define access policies to require that users authenticate before they can connect to those services or applications.

Before you add a SAML resource in AuthPoint, you must configure SAML authentication for your third-party service provider. To do this, download the AuthPoint metadata from the Resources page in the AuthPoint management UI and import the metadata file to the third-party service provider.

The AuthPoint metadata provides information that is necessary to identify AuthPoint and establish a trusted relationship between the third-party service provider and the identity provider (AuthPoint).

To configure SAML authentication for your third-party service provider:

1. Select Resources.

2. Click Certificate.
3. On the Certificate Management page, next to AuthPoint certificate you will associate with your resource, click and select an option to download the metadata, copy the metadata URL, download the certificate, or copy the fingerprint based on what the service provider for your resources requires.

   The AuthPoint metadata provides your resource with information necessary to identify AuthPoint as a trusted identity provider. This is necessary for SAML authentication.

4. Import the AuthPoint metadata file to the third-party service provider and get the Service Provider Entity ID and Assertion Consumer Service values from the service provider. These values are necessary to configure the SAML resource in AuthPoint.

   Refer to the AuthPoint Integration Guides for the steps to configure specific SAML resources.

To add a SAML resource in the AuthPoint management UI:

1. Select Resources.

2. Click Add Resource.
   
   The Add Resource page opens.

3. From the Type drop-down list, select SAML.
4. In the Name text box, type a name for the resource. We recommend you use the name of the application.
5. From the Application Type drop-down list, select the relevant application, or select Others if the application is not listed. For the Others application type, you can specify the relay state, custom attributes, and a custom image to appear for this application in the IdP portal.

   You can click the Integration Guide link to open a help topic with the steps to set up your application. This link is context sensitive.

6. (Optional) If you selected the Others application type, you can specify a Relay State parameter for this SAML resource.
7. In the Service Provider Entity ID and Assertion Consumer Service text boxes, type the values from the service provider of the application.
8. From the User ID drop-down list, select which user ID attribute to send to the service provider. The service provider compares the user ID attribute for the AuthPoint user with the user name in your application. These values must match.

   For example, Salesforce requires a user name in an email format that includes a domain. Because the AuthPoint user name does not include a domain, your user ID must be email to match the Salesforce user name.

9. (Optional) Click Choose File to upload a certificate from the service provider. When you upload a certificate, you can select the Encryption enabled toggle to enable or disable encryption for the SAML communication.
10. 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. The AuthPoint certificate provides your resource (service provider) with the information necessary to identify AuthPoint as a trusted identity provider. If you have not replaced the default AuthPoint certificate for your account, you can leave the default value. For more information, see Certificate Management.
11. Some application types require additional information. If applicable, complete any additional fields required for the application.
12. (Optional) If you selected the Others application type, you can specify one or more custom attributes for this SAML resource. This is necessary for some applications. To add a custom attribute:
    1. Click Add Attribute.
       The Add Attribute window opens.
    2. Enter the Attribute Name. This value is case-sensitive.
    3. From the Get Value From drop-down list, select what value is used for this custom attribute. If the value is static, select Fixed value and specify the fixed value to use.
    4. Click Save.
13. (Optional) If you selected the Others application type, you can upload a custom image to appear for this application in the IdP portal. To upload an image, drag an image file from your computer, or click Select a file to import and select an image file.
14. Click Save.

To add a Logon app resource

Do not install the Logon app on computers that run Windows 7 or lower or on servers that run Windows 2008 R2 or lower.

The Logon app enables you to require authentication when users log in to a computer or server. This includes protection for RDP and RD Gateway.

There are two parts to the Logon app:

• The resource you configure in AuthPoint
• The application you install on a computer or server

When you install the Logon app, authentication is required to log in. On the login screen, users must type their password and then select one of the allowed methods of authentication (push notification, one-time password, or QR code).

If your AuthPoint license expires or you delete your Logon app resource, users can log in to their computers with only their password.

To start, you must add a resource for the Logon app:

1. From the AuthPoint navigation menu, select Resources.

2. Click Add Resource.
   
   The Add Resource page opens.

3. From the Type drop-down list, select Logon App.
   Additional fields appear.

4. In the Name text box, type a name for this resource.
5. (Optional) In the Support Message text box, type a message to show on the logon screen.

6. From the Access for Non-AuthPoint Users drop-down list, select whether to allow users who do not have an AuthPoint user account to log in to protected computers without MFA. You can choose from three options:
   • Do not allow non-AuthPoint users
   • Allow specific non-AuthPoint users to log in without MFA
   • Allow all non-AuthPoint users to log in without MFA

   Non-AuthPoint users can only log in without MFA if an AuthPoint user account with the same user name does not exist.

7. If you chose to allow specific non-AuthPoint users to log in without MFA, in the Add User Names text box, type the user name of each non-AuthPoint user that can log in without MFA. You can specify up to 50 non-AuthPoint users that can log in without MFA.

8. Click Save.

You do not have to add additional Logon app resources for each computer that the Logon app is installed on, regardless of the OS. You only need multiple Logon app resources if you have multiple domains.

Now that you have added a Logon app resource, you must install the Logon app on any computers and servers that you want to require authentication for. The steps in the next procedure cover how to manually install the Logon app. You can also install the Logon app from a Windows command prompt or use an Active Directory GPO to install the Logon app remotely on multiple computers. For detailed steps, see Install the Logon App from a Windows Command Prompt and Use an Active Directory GPO to Install the Logon App.

To install the Logon app:

1. Select Downloads.
2. In the Logon App section, next to your operating system, click Download Installer.
3. Click Download Config to download the configuration file for the Logon app.

   You can use the same configuration file for every installation of the Logon app on the same domain, regardless of the OS.

4. On your computer, move the downloaded configuration file to the same directory as the Logon app installer (.MSI or .PKG file).
5. Run the Logon app installer and install the Logon app.

   When you install the Logon app, the computer you install the Logon app on must connect to the Internet before the user logs on for the first time. This is required so that the Logon app can communicate with AuthPoint to check the authentication policies.

To add an IdP portal resource

The Identity Provider (IdP) portal resource is a portal page that shows users a list of SAML resources available to them. It makes it easier for users to get access to resources. Users log in to the IdP portal and see each resource they have access to.

If you enable the feature, users can also log in to the IdP portal to activate hardware and software tokens.

When you add the IdP portal resource to an authentication policy, the SSO login page redirects users in the groups added to that authentication policy to the portal page.

To set up AuthPoint with an IdP portal:

1. Select Resources.

2. Click Add Resource.
   The Add Resource page opens.

3. From the Type drop-down list, select IDP Portal.
4. In the Name text box, type a descriptive name for the resource.
5. In the Account Alias text box, type a unique value to append to the URL for your IdP portal. The URL for the IdP portal is always https://authpoint.watchguard.com/<account_alias>. In our example, the account alias is washington, so the URL for the IdP portal is https://authpoint.watchguard.com/washington.
6. To allow users to activate hardware and software tokens from the IdP portal, enable the Allow users to manage their tokens from the IdP portal toggle.
7. Click Save.

   Multiple authentication policies can use the same IdP Portal resource. You do not have to add additional IdP resources in AuthPoint.

To add a RESTful API Client resource

The Authentication API is a RESTful API that you can use to add the protection of AuthPoint MFA to custom applications. To use the Authentication API, you must configure a RESTful API Client resource in the AuthPoint management UI. This resource represents your API client, and is used to configure authentication policies that determine how your users can authenticate.

For detailed steps to configure an resource, see Configure MFA for a RESTful API Client.

To add an RD Web resource

Remote Desktop Web Access is a page that shows a list of applications published from a server. From the page, you can click the icon for an application to launch that application.

The AuthPoint agent for RD Web adds the protection of multi-factor authentication to RD Web Access. When you configure the agent for RD Web, users must authenticate with AuthPoint MFA to connect to the RD Web page.

There are two parts to configure MFA for RD Web:

• The resource you configure in AuthPoint
• The agent you install on the RD Web server

For detailed steps to configure MFA for RD Web, see About the AuthPoint Agent for RD Web.

To add an ADFS resource

Active Directory Federation Services (ADFS) is a single sign-on solution for Active Directory that enables users to log in to external systems and applications with their Active Directory credentials. It provides users with a single sign-on experience when they log in to their organization’s web based applications.

With the AuthPoint ADFS agent, you can add multi-factor authentication (MFA) to ADFS for additional security. To do this, you must add an ADFS resource in the AuthPoint management UI and install the ADFS agent on your ADFS server.

For detailed steps to configure MFA for ADFS, seeConfigure MFA for ADFS.

After you add and configure resources in AuthPoint, you must create groups for your users. In AuthPoint, groups are how you define which resources your users have access to. You add users to groups in AuthPoint, then you add the groups to the authentication policies that specify which resources users can authenticate to.

You must add at least one group before you can add authentication policies or add users to AuthPoint.

To sync external groups from Active Directory or Azure Active Directory, you must add an external identity and create a group sync with the Create new synchronized groups option enabled. This is covered in Step 9 — Sync users from your LDAP database.

To add a group to AuthPoint, in the AuthPoint management UI:

1. From the navigation menu, select Groups.
2. Click Add Group.

3. In the New Group section, in the Name text box, type a descriptive name for the group.
4. (Optional) In the Description text box, type a description of the group.

5. Click Save.
   Your group is listed on the Groups page.

Policy objects are the individually configurable components of a policy, such as network locations. You configure policy objects and then add them to authentication policies.

You can configure these kinds of policy objects:

Network Locations

Network location policy objects enable you to specify a list of IP addresses. You can then configure authentication policies that only apply when users authenticate from the IP addresses in the specified network location.

Time Schedule

Time schedule policy objects enable you to specify the dates and times when authentication policies apply to user authentications. When you add a time schedule to an authentication policy, the policy only applies when a user authenticates during the specified time schedule.

Geofence

Geofence policy objects enable you to specify a list of countries. You can then configure authentication policies that only apply when users authenticate from those countries. You might do this if you want to enforce different MFA requirements for different locations, or if you want to block authentication from specific countries.

Geokinetics

Geokinetics policy objects enable you to create policy objects that compare the user's current location and the location of their last valid authentication. AuthPoint automatically denies authentications from a location the user could not have travelled to since their previous authentication, based on the distance and time between authentications.

When you add a policy object to an authentication policy, the policy only applies to user authentications that match the conditions of the authentication and the policy objects. For example, if you add a specific network location to a policy, the policy only applies to user authentications that come from that network location.

We recommend that you create a second policy for the same groups and resources without the policy object. Users who only have a policy that includes a policy object do not get access to the resource when the conditions of the policy object do not apply to the authentication (because they do not have a policy that applies, not because authentication is denied).

• 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.
• Users who only have a policy that includes a time schedule do not get access when they authenticate outside the hours of that time schedule.
• Users who only have a policy to allow access that includes a geofence do not get access to the resource when they authenticate outside of the specified countries.

If you have two policies (one with a policy object and one without), assign a higher priority to the policy with the policy object. For more information, see About Policy Precedence.

Geokinetics policy objects work differently than other policy objects because they apply after an authentication is complete. Geokinetics do not affect the conditions of an authentication, so when you add a geokinetics policy object to an authentication policy, you do not have to create a second policy without the geokinetics policy object.

To support authentication with the geofence and geokinetics policy objects, you must install these versions of the AuthPoint agents:

• AuthPoint agent for Windows v2.7.1 or higher
• AuthPoint agent for RD Web v1.4.2 or higher
• AuthPoint agent for ADFS v1.2.0 or higher

RDWeb and ADFS have additional requirements to support authentications with location data. For more information, see Geofence for RD Web and Geofence for ADFS.

These resources do not support geokinetics or geofence:

• AuthPoint agent for macOS
• RADIUS

For RADIUS authentication, policies that include a geokinetics or geokinetics policy object do not apply because AuthPoint cannot determine the IP address of the end user or the origin IP address.

To configure a network location policy object:

Network locations require an Internet connection.

For RADIUS authentication and basic authentication (ECP), policies that include a network location are not applied because AuthPoint cannot determine the IP address of the user or the origin IP address.

1. From the AuthPoint navigation menu, select Policy Objects.

2. Click Add Policy Object.
   
   The Add Policy Object page appears.

3. From the Type drop-down list, select Network Location.
   
   Additional fields appear.
4. In the Name text box, type a name to identify this network location policy object. This helps you identify the network location when you add it to authentication policies.
5. In the IP Mask text box, type a public IP address or netmask that defines the range of public IP addresses for this network location and press Enter or Return. You can specify multiple IP addresses and ranges for one network location.

   AuthPoint only supports IPv4 addresses for network locations.

   You cannot add the IP addresses 0.0.0.0 or 255.255.255.255 to a network location.

6. Click Save.

To configure a time schedule policy object:

1. From the AuthPoint navigation menu, select Policy Objects.

2. Click Add Policy Object.
   
   The Add Policy Object page appears.

3. From the Type drop-down list, select Time Schedule.
   
   Additional fields appear.
4. In the Name text box, type a name for this time schedule policy object. This helps you identify the time schedule when you add it to authentication policies.
5. From the Time Zone drop-down list, select the time zone that you want to use for this time schedule.
6. If you want to adjust the selected time zone for daylight saving time, select the Adjust for daylight saving time check box. When you select this option, the time policy immediately adjusts the selected time zone by plus one hour. For example, a time schedule with the time zone set to Pacific Standard Time, which is UTC -8 hours, immediately adjusts to UTC -7 hours (-8 hours + 1 hour).

   AuthPoint does not dynamically adjust for daylight saving time. You must select the Adjust for daylight saving time check box when daylight saving time applies, and clear the check box when daylight saving time does not apply.

7. Select an option to specify whether you want to add specific days of the week or a specific date to this time schedule.
   • Days of the week — To add specific days of the week to the time schedule, select this option and select the days to include.
   • Dates — To add a specific date to the time schedule, select this option and use the Date field to select the date. You can add only one date at a time.

   You can add only one option at a time. To add multiple sets of weekdays and one or more dates to the same time schedule, you must add them separately.

8. Enter the Start Time and End Time for when you want the time schedule to apply on the selected days or date. These values must be between 00:00 and 23:59, and the End Time must be later than the Start Time.

   The time zone that you select in Step 5 applies to the start and end times for all schedules that you add to the policy object.

9. To add the days and times to your time schedule, click Add. To add additional days or dates, or to specify additional time periods for the same days or dates, repeat Steps 7 — 9.
10. Click Save.

To configure a geofence policy object:

1. From the AuthPoint navigation menu, select Policy Objects.

2. Click Add Policy Object.
   
   The Add Policy Object page appears.

3. From the Type drop-down list, select Geofence.
   Additional fields appear.
4. In the Name text box, type a name to identify this geofence policy object. This helps you identify the geofence when you add it to authentication policies.
5. From the Countries list, select one or more countries to add to this geofence. You can type text to narrow the available options.
6. If you want this geofence to apply to user authentications with low accuracy location data, select the Allow location data with low accuracy check box. This option increases the margin for error that AuthPoint uses to validate location data. For example, if you configure a geofence that only applies to user authentications from Canada, but you allow location data with low accuracy, AuthPoint might accept an authentication from a user just beyond the border in the United States.

   Location data with low accuracy is required for RDP connections, Firebox resources, Windows virtual machines (VMs), and authentications with location data based on IP address.

7. Click Save

To configure a geokinetics policy object:

1. From the AuthPoint navigation menu, select Policy Objects.

2. Click Add Policy Object.
   
   The Add Policy Object page appears.

3. From the Type drop-down list, select Geokinetics.
   
   Additional fields appear.
4. In the Name text box, type a name to identify this geokinetics policy object. This helps you identify the geokinetics when you add it to authentication policies.

5. In the Velocity text box and the adjacent drop-down list, specify a number and unit for AuthPoint to use for this geokinetics policy object. AuthPoint denies authentications if the distance between the current authentication and the previous authentication cannot be travelled at this speed.

   The default velocity is 600 miles per hour (the average speed of a commercial airplane).

6. (Optional) In the Exceptions text box, enter a public IP address or netmask that defines a range of public IP addresses that AuthPoint should ignore for this geokinetics policy object, then press Enter or Return. You can specify multiple exceptions. You might do this so that the geokinetics policy object does not deny authentications when users connect to a VPN.

7. If you want AuthPoint to consider authentications that have location data with low accuracy when this geokinetics policy object is considered, select the Consider authentications that have location data with low accuracy check box.

   If you do not select this check box, authentications that have location data with low accuracy are not evaluated against the geokinetics policy object.

8. Click Save.
9. Add this geokinetics policy object to the authentication policies that you want it to apply to. For more information, see About AuthPoint Authentication Policies.

   Unlike other policy objects (geofence, time schedule, network locations), when you add a geokinetics policy object to an authentication policy, you do not have to create a second policy without the geokinetics policy object.

After you add all your resources and groups in AuthPoint, you must configure authentication policies. Authentication policies specify which resources AuthPoint users can authenticate to and which authentication methods they can use (Push, QR code, and OTP).

When you configure an authentication policy, you specify:

• Whether the policy allows or denies authentications.
• Which authentication methods are required.
• Which resources the policy applies to.
• Which user groups the policy applies to.
• Which policy objects apply to the authentications.

A user who is not a member of a group that has an authentication policy for a specific resource cannot authenticate to log in to that resource.

When you configure policies, make sure you follow these requirements and recommendations:

• You must configure at least one group before you can configure authentication policies.
• For RADIUS authentication and basic authentication (ECP Enhanced Client or Proxy), policies that have a network location do not apply because AuthPoint does not have the IP address of the user or the origin IP address.
• Policies with policy objects only apply to user authentications that match the conditions of all policy objects. Users who only have a policy that includes policy objects do not get access to the resource when the conditions of the policy objects do not apply to the authentication. This is because they do not have a policy that applies, not because authentication is denied.
  • Policies with network locations Network location policy objects are a list of IP addresses that you configure. only apply to user authentications that come from that network location. Users who only have a policy that includes a network location cannot access the resource when they authenticate outside of that network location.
  • Policies with geofences Geofence policy objects specify the a list of countries. Policies only apply to user authentications from the specified countries. only apply to user authentications that come from a country specified in the geofence policy object. Users who only have a policy that includes a geofence cannot get access to the resource when they authenticate outside of the specified countries.
  • Policies with time schedules Time schedule policy objects specify the dates and times when an authentication policy applies to user authentications. only apply to user authentications during the specified time schedule. Users who only have a policy that includes a time schedule cannot access the resource when they authenticate outside the hours of that time schedule.
  • Policies with geokinetics Geokinetics policy objects enables you to create policy objects that compare the user's current location and the location of their last valid authentication. AuthPoint automatically denies authentications from a location the user could not have travelled to since their previous authentication, based on the distance and time between authentications. do not affect the conditions of an authentication.
• If you configure policy objects Policy objects are the individually configurable components of a policy, such as network locations., we recommend that you create a second policy for the same groups and resources without the policy objects. Assign a higher priority to the policy with the policy objects.

  Geokinetics policy objects work differently than other policy objects because they apply after an authentication is complete. Geokinetics do not affect the conditions of an authentication, so when you add a geokinetics policy object to an authentication policy, you do not have to create a second policy without the geokinetics policy object.

• Geokinetics policy objects are not applied for Logon app, RD Web, and ADFS resources if the authentication policy requires only a password (no MFA). This is because AuthPoint validates geokinetics after the authentication. In scenarios where AuthPoint does not validate the password, no authentication request is sent to AuthPoint.
• If you enable the push and OTP authentication methods for a policy, RADIUS resources associated with that policy use push notifications to authenticate users.
• You must enable the push authentication method for policies with MS-CHAPv2 RADIUS resources.
• RADIUS resources do not support QR code authentication.

To configure an authentication policy:

1. Select Authentication Policies.
2. Click Add Policy.

3. Type a name for the policy.
4. From the Select the authentication options drop-down list, select an option to specify whether to require MFA or to deny authentications for this policy.
   • Authentication options — Require MFA when users in the groups associated with this policy authenticate to the resources associated with this policy.
   • Authentication not allowed — Deny authentications when users in the groups associated with this policy try to authenticate to the resources associated with this policy

5. If you require MFA for this policy, select the check box for each authentication option users can select from when they authenticate. For more information about authentication methods, see About Authentication.

   If you enable the push and OTP authentication methods for a policy, RADIUS resources associated with the policy use push notifications to authenticate users.

   QR code authentication is not supported for RADIUS resources.

6. For policies that include an Microsoft 365 resource, if you require authentication for a device or resource that is part of your Microsoft 365 domain but cannot use MFA, such as a printer, select the Basic Authentication check box. Basic authentication is also called Enhanced Client or Proxy (ECP).
7. From the Groups drop-down list, 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.
8. From the Resources drop-down list, select which resources this policy applies to. To configure this policy to apply to all resources, select All Resources.

9. From the Policy Objects drop-down list, select which policy objects apply to this policy. For more information about policy objects, see About Policy Objects.

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

    After 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.

To sync users from an LDAP database, you must create a query for the external identity that you added. The queries you add to an external identity specify which users to sync from your Active Directory or LDAP database. They pull user information from the database and create AuthPoint users for the users that match the query.

There are two ways to query users:

• Group Sync — Select the LDAP groups you want to sync users from and AuthPoint creates the query for you.
• Advanced Queries — Create your own LDAP queries to specify which groups or users to sync.

In this example, we show the steps to use the group sync feature.

Before you continue, make sure that each user account has a valid email address. If the email address for a user account is not correct, the user cannot receive the email message to set a password and activate a token.

Before you continue, be aware of these requirements:

• If the selected LDAP groups have more users than you have available AuthPoint licenses for, the sync only creates as many users as your license supports
• LDAP users that do not have a first name, user name, or email address are not included in the synchronization
• If the email address for a user account is not correct, the user cannot receive the email message to set a password and activate a token
• We recommend that you do not add the same LDAP group to multiple group syncs or create multiple group syncs that include the same LDAP user

To sync LDAP groups:

1. Select External Identities.
2. Next to your external identity, click and select Group Sync.

3. On the Group Sync page, click Add New Group to Sync.

4. In the Add Group Sync window, from the Select LDAP Groups to Sync Users From drop-down list, select the LDAP groups you want to sync users from. You can select multiple groups.

5. To create new groups in AuthPoint based on the Active Directory groups that you sync users from, enable the Create new synchronized groups toggle. If you enable this option, users sync to the new groups based on group membership in the LDAP database, in addition to the selected AuthPoint group. Do not add the same LDAP group to multiple group syncs or create multiple group syncs that include the same LDAP user.

   This option is only available for Active Directory and Azure Active Directory LDAP databases. To use this feature, you must install version 6.1 or higher of the AuthPoint Gateway.

   The option to create new synchronized groups in AuthPoint does not include Active Directory groups that are not specified in the group sync. If a synced user is a member of an Active Directory group that is not specified in the group sync, that Active Directory group will not be created in AuthPoint.

6. From the Select an AuthPoint Group to Add Users To drop-down list, select the AuthPoint group to add the users to.

   For each group sync, all users are added to the same AuthPoint group. To add LDAP users to multiple groups, we recommend that you enable the Create new synchronized groups toggle and use your Active Directory group structure to manage your users.

7. If you do not want AuthPoint to create mobile tokens for these user accounts or send an email to the users to activate their mobile tokens, clear the Automatically assign a mobile token to the synced users and Automatically send the activation email for the synced users check boxes.

   You cannot change these settings after you sync the user accounts. To assign a token to a user that does not have these options selected, you must resend the Token Activation email. For more information, go to Resend Activation Email.

8. Click Save.
   The Add Group Sync window closes.

After you add a query to find your users (manually or with group sync), AuthPoint syncs with your Active Directory or LDAP database at the next synchronization interval This is defined in the Synchronization Interval drop-down list on the LDAP Configuration page for your external identity. and creates an AuthPoint user account for each user identified by the query.

To start a sync immediately, on the External Identities page, next to the your external identity, click and select Start Synchronization.

The created user accounts appear on the Users page with a green Activated status icon next to the user name. The Activated status icon indicates that the user has been created and is currently active (not blocked). You can identify users synced from an external identity by the LDAP tag in the Type column in the list of users.

Each user receives an email that they use to activate their token in the AuthPoint mobile app. When a user activates their token, their token information is shown in the Token column with a green Activated status icon next to the token.

Users synced from an external identity use their existing password for authentication. They do not receive the email to set an AuthPoint password.

If you enabled the Create new synchronized groups toggle, the synced groups are created in AuthPoint. The newly created groups appear on the Groups page. You can identify synced groups from Active Directory by the LDAP tag in the Type column in the list of groups.

If you change the name of a synced group in Active Directory, the name of the synced group in AuthPoint updates automatically to match. You cannot edit the synced groups in AuthPoint.

If you delete the group in Active Directory, or if you delete the group sync, the synced group is not deleted in AuthPoint. You must manually delete the synced group in AuthPoint.

You can create Corporate Credentials to share a direct link to a specific website with specific user groups. You might do this for websites or applications that do not support SAML or that are not managed by your company. For example, you might create Corporate Credentials to provide users with a link in the IdP portal to the website they use to manage their 401k accounts.

When you create Corporate Credentials, you can choose to share the login credentials for that website or account. For example, you might share the credentials to a corporate social media account with your marketing team.

Corporate Credentials are available in the IdP portal for users who are members of the groups that the Corporate Credentials are shared with. If you choose to share login credentials, the Corporate Credentials are also available in the password vault. For more information about password management see Password Management.

If you share login credentials, each user must accept the shared Corporate Credentials in the password manager.

To add Corporate Credentials:

1. Select Corporate Credentials.
   The Corporate Credentials page opens.

2. Click Add Corporate Credential.
   The Add Corporate Credential page opens.

3. In the Name text box, enter a name to identify this corporate credential to users in the IdP portal and their password vault.
4. In the URL text box, enter the URL for the application or service. If you do not specify a protocol in the URL, AuthPoint uses HTTPS by default.
5. To upload an image to identify the corporate credential in the IdP portal, drag an image file from your computer to the Image box, or click Select a file to import and select an image file.

6. From the Groups list, select the groups this corporate credential is available to.
   You can select more than one group. To make this corporate credential available to all groups, select All Groups.
7. To share login credentials so that users can log in to a specific account, select the Share credentials for this corporate credential check box. When you select this option, the corporate credential is available in the password vault of specified users in addition to the IdP portal. If you select this option, when users click the link in the IdP portal, they log in to the specified website automatically with the login credentials that you specify.

   After you save the corporate credential, you cannot change whether the credentials are shared.

8. If you chose to share credentials, enter the User Name and Password for the account.

9. Click Save.
   The Corporate Credentials page opens.

After you save the Corporate Credentials, a new tile shows in the IdP portal for users who are members of the groups that you shared the Corporate Credential with. Users can click this tile to go to the URL you specified.

AuthPoint Total Identity Security includes a Dark Web Monitor service to help you monitor and protect your domains. With the Dark Web Monitor service, WatchGuard actively monitors data breaches for up to three of your domains. If a data breach is found to include your email addresses and domains, you are notified.

When you add a domain, you must select one of these email addresses for authorization requests:

• security@<yourdomain>
• webmaster@<yourdomain>
• postmaster@<yourdomain>
• hostmaster@<yourdomain>

To make sure that you own the domain, WatchGuard sends an authorization request to the selected email address. You cannot specify a custom email address for authorization requests. If you do not have any of these email addresses for the domain, you must create one.

To configure Dark Web Monitor for a domain, in WatchGuard Cloud:

1. Select Administration > Dark Web Monitoring.
   The Dark Web Monitoring page opens.

2. Click Add Domain.
   The Add Domain page opens.

3. In the Domain text box, enter your domain name, such as example.com.
4. From the Email drop-down list, select the email address you want to send authorization requests to. Authorization is required to monitor data breaches for the domain, and to update Dark Web Monitor domain settings in WatchGuard Cloud.

   You cannot specify a custom email address for authorization requests. If none of the listed email addresses exist, you must create one.

5. Select the email addresses you want to receive notifications when Dark Web Monitor detects a data breach that includes an email address from your domain. You must select at least one email address.
   If you select the breached email address, the UI gives you the option to include the exposed password (and any other sensitive data) in the email message that is sent to the breached email address. If you choose to include the exposed password, this information is not sent to any other selected email addresses.

   To send a notification to the authorization email address, you must select the check box next to that email address.

6. (Optional) To send notifications to other email addresses, in the Additional Emails text box, type the email address and press the Enter key. You can specify up to 10 email addresses to send notifications to.

7. Click Save.