Cisco ASA L2TP VPN Integration with AuthPoint

Deployment Overview

This document describes how to set up AuthPoint multi-factor authentication (MFA) for Active Directory users that use Cisco® ASA (Adaptive Security Appliance) with an L2TP VPN client.

Your Cisco ASA unit must already be configured and deployed before you set up MFA with AuthPoint.

If the L2TP VPN client is only used by local AuthPoint users, you do not have to configure Microsoft NPS or enable MS–CHAPv2. NPS is only required for users synced from Active Directory or an LDAP database.

Users synced from Azure AD cannot authenticate to RADIUS client resources that use MS-CHAPv2.

Cisco ASA Configuration for RADIUS Authentication

AuthPoint communicates with various cloud-based services and service providers with the RADIUS protocol. This diagram shows an overview of the configuration required for RADIUS authentication.

Before You Begin

Before you begin these procedures, make sure that:

• You have installed and configured Active Directory Domain Services.
• You have installed Network Policy and Access Services, which includes Network Policy Server (NPS).

Configure Microsoft NPS Server

To enable users synced from Active Directory to successfully authenticate with MS-CHAPv2, you must configure Microsoft Network Policy Server (NPS). NPS is required to validate the user credentials from MS-CHAPv2 RADIUS requests against Active Directory.

In our example, Active Directory and NPS are installed on the same server. If NPS is installed on a different server than Active Directory, you must register NPS in the Active Directory domain and log in as a domain administrator.

For instructions to configure Active Directory Domain Services, see the Microsoft documentation for Active Directory.

If the L2TP VPN client is only used by local AuthPoint users, you do not have to configure Microsoft NPS. Continue to the Configure the Cisco ASA Unit section.

1. On the Windows server, run Server Manager.
2. Select Tools > Network Policy Server.
   The Network Policy Server console appears.
3. Select RADIUS Clients and Servers > RADIUS Clients.
4. Right-click RADIUS Clients and select New.
   The New RADIUS Client window appears.
5. In the Friendly name text box, type a name.
6. In the Address (IP or DNS) text box, type the IP address of the AuthPoint Gateway. In our example, the IP address of the AuthPoint Gateway is 192.168.100.20.
7. In the Shared secret and Confirm shared secret text boxes, type a shared secret key. This key is used to communicate with the RADIUS server (AuthPoint Gateway).

   You must use the same shared secret key when you configure your RADIUS client and your RADIUS client resource.



8. Click OK.



9. Select Polices > Connection Request Policies. Make sure the default policy is enabled.



10. Right-click Network Policies and select New.
    The New Network Policy window appears.
11. In the Policy Name text box, type a name for this policy. In our example, we type ecotest.
12. Click Next.
13. In the Specify Conditions section, click Add.
14. Select User Groups. Click Add > Add Groups.
15. In the Enter the object name to select text box, type the group name. The name of this group must match the name of the Active Directory group your users belong to.
16. Click OK.
17. Click OK.
18. Click Next.



19. Click Next.
20. In the Configure Authentication Methods section, clear the User can change password after it has expired check box.
21. Click Next.



22. Click Next.
23. In the Configure Settings section, click Add. In our example we use group authentication. If you want to use user authentication, skip Steps 23-29.
24. From the Attributes list, select Filter-Id. Click Add.
25. Click Add.
26. In the Attribute Information window, in the text box type a group name. The name of this group must match the name of the Active Directory group your users belong to.



27. Click OK.
28. Click OK.
29. Click Close.
30. Click Next.



31. Click Finish.



32. Right-click NPS (Local) and select Register server in Active Directory.
33. Click OK.
34. Click OK.

Configure the Cisco ASA Unit

Follow these steps to configure the Cisco ASA unit.

Add the AuthPoint Gateway to the AAA Server Groups

1. Start Cisco Adaptive Security Device Manager (ASDM) and log in to Cisco ASA.
2. Select Configuration.
3. Select Device Management > Users/AAA > AAA Server Groups.
   



4. Next to the AAA Server Groups section, click Add.
   The Add AAA Server Group window appears.
5. In the AAA Server Group text box, type a name for the server group. In our example, we type AuthPointGroup.



6. Click OK to save the AAA server group. Leave the default value for other settings.
7. From the AAA Server Groups list, select the AAA Server group you created.



8. Next to the Servers in the Selected Group section, click Add to add an AAA Server for the selected AAA Server group.
   The Add AAA Server window appears.
9. From the Interface Name drop-down list, select opt1. This is the interface for connections to the AuthPoint Gateway.
10. In the Server Name or IP Address text box, type the IP address of the AuthPoint Gateway.
11. In the Timeout text box, type 60.
12. In the Server Authentication Port text box, type 1812.
13. In the Server Accounting Port text box, type 1813.
14. In the Server Secret key text box, type the shared secret key that you specified in the Configure Microsoft NPS Server section. This is the password that the RADIUS server (AuthPoint Gateway) and the RADIUS client (Cisco ASA) will use to communicate.

    You must use the same shared secret key when you configure your RADIUS client resource in AuthPoint.



15. Click OK to save the AAA Server settings.
16. Click Apply.

Configure the L2TP VPN Address Pool

1. Select Configuration.
2. Select Remote Access VPN > Network (Client) Access > Address Assignment > Address Pools.
3. Click Add > IPv4 Address Pool.
   The Add IPv4 Pool window appears.
4. In the Name text box, type a name.
5. In the Starting IP Address text box, type the start IP address.
6. In the Ending IP Address text box, type the ending IP address.
7. In the Subnet Mask text box, type the subnet mask.



8. Click OK.
9. Click Apply.

Configure L2TP VPN

1. Select Wizards > VPN Wizards > IPSec (IKEv1) Remote Access VPN Wizard.



2. From the VPN Tunnel Interface drop-down list, select outside. This is the external interface of the Cisco ASA unit.
3. Click Next.

10. Click Next.
11. For VPN Client Type, select Microsoft Windows client using L2TP over IPsec.
12. Select the MS-CHAP-V2 check box.



13. Click Next.
14. Select Pre-Shared Key.
15. In the Pre-Shared Key text box, type a pre-shared key. You must specify this same key when you configure the VPN client.



16. Click Next.
17. Select Authenticate using an AAA server group.
18. From the AAA Server Group Name drop-down list, select the group you created in the previous section.



19. Click Next.
20. From the Pool Name drop-down list, select the pool you created in the previous section.



21. Click Next.
22. In the Primary DNS Server and Secondary DNS Server text box, type the IP address of the DNS server.



23. Click Next.
24. From the Interface drop-down list, select opt1.
25. In the Exempt Networks, add opt1-network/24.



26. Select Enable split tunneling to let remote users have simultaneous encrypted access to resources defined above, and unencrypted access to the internet.
27. Select Enable Perfect Forwarding Secrecy (PFS).
28. From the Diffie-Hellman Group drop-down list, select 1.



29. Click Next.
30. Click Finish.
31. Click Save.

Configure Firewall ACL

1. Select Configuration.
2. Select Firewall > Advanced > ACL Manager.
3. Click +Add > Add ACL.
   The Add ACL window appears.



4. In the ACL Name text box, type a name of the ACL. The ACL name must match the Filter-id you set in the Connection Request Policies Settings in your NPS server.



5. Click OK.
6. Select the ACL you just created.
7. Click +Add > Add ACE.
   The Add ACE window appears.
8. Select Permit.
9. From the Source and Destination drop-down lists, select any.
10. From the Service drop-down list, select ip. You can choose to select another service to use if you want.



11. Click OK. Leave the default value for other settings.
12. Click Apply.

Configure AuthPoint

Before AuthPoint can receive authentication requests from your Cisco ASA unit, you must:

• Specify your Cisco ASA unit as a RADIUS client resource In AuthPoint, resources are the applications and services that your users connect to. in AuthPoint.
• Add an authentication policy Authentication policies specify which resources users can authenticate to and which authentication methods they can use (Push, QR code, and OTP). for the Cisco ASA RADIUS client resource or add the Cisco ASA RADIUS client resource to an existing authentication policy.
• Bind the Cisco ASA RADIUS client resource to the AuthPoint Gateway.

Add a RADIUS Client Resource in AuthPoint

From the AuthPoint management UI:

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

2. From the Type drop-down list, select RADIUS Client.
   Additional fields appear.

3. In the Name text box, type a descriptive name for the resource.
4. 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.
5. From the Value sent for RADIUS attribute 11 (Filter-Id) 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.
6. In the Shared Secret text box, type the shared secret key that you specified in the Configure Microsoft NPS Server section. This is the password that the RADIUS server (AuthPoint Gateway) and the RADIUS client will use to communicate.
7. Click the Enable MS-CHAPv2 toggle.
   Additional fields appear.

   If the L2TP VPN client is only used by local AuthPoint users, you do not have to enable MS–CHAPv2. Continue to Step 11.

8. 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.
9. In the Port text box, type 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.

10. In the Timeout In Seconds text box, type 60.



11. 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 group to AuthPoint:

1. From the navigation menu, select Groups.
2. Click Add Group.
   The New Group page appears.

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

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 Cisco ASA 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.
   The Authentication Policies page opens.

2. Click Add Policy.
   The Add Policy page opens.

3. In the Name text box, type a name for this policy.
4. From the Select the Authentication Options drop-down list, select Authentication Options, then select which authentication options users can choose from when they authenticate.

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

   QR code authentication is not supported for RADIUS client resources.

5. 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.
6. From the Resources drop-down list, 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.

7. (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 match 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).

   For RADIUS authentication, policies that have a Network Location do not apply because AuthPoint does not have the IP address of the user.

   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.

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

Bind the RADIUS Resource to a Gateway

To use RADIUS authentication with AuthPoint, you must have the AuthPoint Gateway installed on your corporate network and you must assign your RADIUS resources to the Gateway in the AuthPoint management UI. The Gateway functions as a RADIUS server.

If you have not already configured and installed the AuthPoint Gateway, see About Gateways.

To assign your RADIUS resources to the Gateway:

1. From the navigation menu, select Gateway.
2. Select the Name of the Gateway.

3. From the RADIUS section, in the Port text box, type the port number used to communicate with the Gateway. The default 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 drop-down list, select your RADIUS client resource.
5. Click Save.

Sync Users to AuthPoint from Active Directory

You must create AuthPoint user accounts for your users. To sync users from Active Directory, you must add an LDAP external identity and create one or more queries.

In AuthPoint, LDAP external identities represent external user databases. They connect to user databases to get user account information and validate passwords. The queries you add to an external identity specify which users to sync from your Active Directory or LDAP database. They pull user information and create AuthPoint user accounts for the users that are found.

For detailed instructions to sync users from Active Directory, see Sync Users from Active Directory or LDAP.

Test the Integration

To test AuthPoint MFA, you can authenticate with a mobile token on your mobile device. For RADIUS resources with MS-CHAPv2 enabled, you authenticate with a push notification (you receive a push notification in the mobile app that you must approve to authenticate).

1. From a Windows 10 computer, select Settings.
2. Select Network & Internet.
3. Select VPN.
4. Click Add a VPN connection.
   The Add a VPN connection window opens.
5. From the VPN provider drop-down list, select Windows (built-in).
6. In the Connection name text box, type a name. In our example, we type l2tp.
7. In the Server name or address text box, type the Cisco ASA WAN port IP address.
8. From the VPN type drop-down list, select L2TP/IPsec with pre-shared key.
9. In the Pre-shared key text box, type the pre-shared key. This must be the same pre-shared key that you configured in the Configure L2TP VPN section.
10. From the Type of sign-in info drop-down list, select User name and password.
11. Click Save.
    The Add a VPN connection window closes.
12. Select the VPN you created. Click Connect.
13. Type your user name and password.
14. Approve the authentication request that is sent to your mobile device.
    The VPN connects successfully.