Two-factor authentication for WatchGuard Access Portal

Overview

LoginTC protects access to your WatchGuard Access Portal using SAML SSO. The LoginTC AD FS Connector protects access to your Microsoft Active Directory Federation Services (AD FS) by adding a second factor LoginTC challenge to existing username and password authentication. The LoginTC AD FS Connector provides a LoginTC multi-factor authentication (MFA) method to your AD FS deployment, used by your WatchGuard Access Portal.

User Experience

After clicking on LoginTC from the WatchGuard Access Portal and entering the username and password into the AD FS login page, the user is shown a selection of second factor options. The user clicks a button to receive a LoginTC push notification, authenticates and is logged in.

Architecture

Authentication Flow

1. A user attempts access to WatchGuard Access Portal with username / password
2. A SAML request is made to AD FS
3. The username / password is verified against an existing first factor directory (i.e. Active Directory)
4. The request is trapped by LoginTC AD FS Connector and an authentication request is made to LoginTC Cloud Services
5. Secure push notification request sent to the user’s mobile or desktop device
6. User response (approval or denial of request) sent to LoginTC Cloud Services
7. The LoginTC AD FS Connector validates the user response
8. User is granted access to WatchGuard Access Portal

Prerequisites

Before proceeding, please ensure you have the following:

• WatchGuard appliance with Access Portal support
• WatchGuard Fireware 12.1.1
• LoginTC Admin Panel account
• Active Directory Federation Services (AD FS) Host, Microsoft Windows Server 2016 (or Windows Server 2012)
• WatchGuard Access Portal configured with federation to your on-premise AD FS

WatchGuard Resources:

• Configure the Access Portal
• About SAML Single Sign-On (SSO)
• SAML Requirements for Identity Providers
• Configure SAML Single Sign-On

LoginTC Domain Creation

Create a LoginTC domain in LoginTC Admin Panel. The domain represents a service (e.g. your corporate AD FS) that you want to protect with LoginTC. It will contain token policies and the users that access your service.

If you have already created a LoginTC domain for your AD FS deployment, then you may skip this section and proceed to Installation.

1. Log in to LoginTC Admin
2. Click Domains:
3. Click Create Domain:
4. Enter a name and optionally pick an icon
5. Scroll down and click Create

Installation

1. Download the latest version of the LoginTC AD FS Connector
2. Run the installer file as a privileged administrator user on the Windows Server with the AD FS role. Also ensure that the AD FS service is running prior to installing.
3. Press Next
4. Read the License Agreement and press Next if you accept the terms.
5. Change the LoginTC API Host only if you have a private enterprise LoginTC deployment. Press Next:
6. Enter your LoginTC Domain ID and Organization API Key. These values are found on your LoginTC Admin Panel. Press Next
7. Press Install. Note that the AD FS service will be restarted during installation and may be temporarily unavailable to your users.

AD FS LoginTC MFA Configuration

To configure your AD FS to use the LoginTC MFA method:

1. Open the AD FS Management console.
2. Click on the Services > Authentication Policies directory in the left side menu.
3. Click on Edit Global Multi-factor Authentication…
4. Check LoginTC in the list of MFA methods.
5. Press Apply then Ok
6. Click on Relying Party Trusts in the left side menu
7. Select the Relying Party you wish to add LoginTC MFA to
   

   Don’t have a Relying Party for WatchGuard Access Portal setup yet?
   For instructions on configuring a Relying Party for Access Portal see sections WatchGuard Access Portal Configuration and AD FS Relying Party.

8. Click on Edit Access Control Policy… under Actions in the right sidebar
9. Select an access control policy that uses MFA (e.g. Permit everyone and require MFA)
10. Press Apply and OK

Your AD FS login will now present the user with a secondary LoginTC authentication page.

Configuration for WatchGuard Access Portal 2FA

Configure WatchGuard Access Portal for SAML Single Sign-On (SSO):

1. Log in to your WatchGuard Fireware Web UI:
2. Under Subscription Services click Access Portal:
3. Click Enable Access Portal:
4. Click on the User Connection Settings tab:
5. Scroll down and click Configure:
6. Click on the SAML tab:
7. Click Enable SAML:
8. Complete the Service Provider (SP) Settings configuration:

Service Provider (SP) Settings:

Property	Explanation	Example
IdP Name	Name to appear as the authentication server name	LoginTC
Host Name	A fully qualified domain name that resolves to the Firebox external interface	watchguard.example.com

8. (Continued) Complete the Service Provider (SP) Settings configuration:

Identity Provider (IdP) Settings

Property	Explanation	Example
IdP Metadata URL	AD FS Federation Metadata URL	https://fs.example.com/FederationMetadata/2007-06/FederationMetadata.xml
Group Attribute Name	The name of the attribute returning group claims	memberOf

9. Click SAVE
10. Navigate to SAML 2.0 Configuration for WatchGuard Access Portal page (i.e. https://watchguard.example.com/auth.saml):
11. Copy the SP metadata URL found under Option 1 and paste in your browser. Save the file as metadata.xml.

AD FS Relying Party

To configure a WatchGuard Access Portal Relying Party in AD FS:

1. Open the AD FS Management console.
2. Click on Relying Party Trusts in the left side menu
3. Click on Add Relying Party Trust…
4. Select Claims Aware
5. Click Start
6. Select Import data about the relying party from a file and then browse the where metadata.xml from the final section of WatchGuard Access Portal Configuration is saved.
7. Click Next
8. Enter a Display name (for example: WatchGuard Access Portal):
9. Click Next
10. Under Choose an access control policy select Permit everyone and require MFA
11. Click Next
12. Click Close
13. Select the Relying Party just created
14. Click on Edit Access Control Policy… under Actions in the right sidebar
15. Select an access control policy that uses MFA (e.g. Permit everyone and require MFA)
16. Press Apply and OK

Next you will need to configured the AD FS Claims for your WatchGuard Access Portal Relying Party.

AD FS Claims

WatchGuard Access Portal requires the following claims to be configured:

Claim 1: LDAP Attribute for SAM-Account-Name

1. Click on Relying Party Trusts in the left side menu
2. Select the WatchGuard Access Portal Relying Party
3. Click on Edit Claims Issuance Policy… under Actions in the right sidebar
4. Click Add Rule
5. Select Send LDAP Attributes as Claims and click Next
6. Enter a Claim rule name (for example, Given Name LDAP Query)
7. Under LDAP Attribute enter SAM-Account-Name
8. Under Outgoing Claim Type enter Given Name
9. Click Finish

Claim 2: Transform Given Name to Name ID

1. Click on Relying Party Trusts in the left side menu
2. Select the WatchGuard Access Portal Relying Party
3. Click on Edit Claims Issuance Policy… under Actions in the right sidebar
4. Click Add Rule
5. Select Transform an Incoming Claim and click Next
6. Enter a Claim rule name (for example, Transform Given Name to Name ID)
7. Under Incoming claim type enter Given Name
8. Under Outgoing claim Type enter Name ID
9. Select Pass through all claim values
10. Click Finish

Claim 3: Group Membership Claim

1. Click on Relying Party Trusts in the left side menu
2. Select the WatchGuard Access Portal Relying Party
3. Click on Edit Claims Issuance Policy… under Actions in the right sidebar
4. Click Add Rule
5. Select Send Group Membership as a Claim
6. Enter a Claim rule name (for example, Send Group Membership as Claim)
7. Under User’s group click Browse and select the group configured for WatchGuard Access Portal
8. Under Outgoing claim type enter memberOf
9. Under Outgoing claim value enter the name of the group. This should match exactly the name configured in the WatchGuard Access Portal
10. Click Finish

With these claims configured you are now ready to test logging into the WatchGuard Access Portal using LoginTC and AD FS.

Logging

The LoginTC AD FS Connector logs events to the Microsoft Event Viewer under Applications and Service Logs → LoginTC. In some cases, it may be helpful to also look at the general AD FS logs under Custom Views → ServerRoles → Active Directory Federation Services.

Uninstallation

To uninstall the LoginTC AD FS Connector, simply navigate to the Add or remove programs in the Windows Control Panel, find LoginTC AD FS Connector in the list and follow the prompts.

Troubleshooting