Firebox Cloud Mobile VPN with IKEv2 Integration with AuthPoint for Microsoft Entra ID Users

The steps to configure AuthPoint and your Firebox Cloud are different based on the Fireware version of your Firebox Cloud. Complete the steps in this section if your Firebox Cloud runs Fireware v12.7.1 or higher.

With Fireware v12.7.1 or higher, you can add AuthPoint as an authentication server on your Firebox Cloud. For this configuration, you must register and connect your Firebox Cloud to WatchGuard Cloud as a locally-managed Firebox or a cloud-managed Firebox. For detailed instructions to register and connect your Firebox Cloud to WatchGuard Cloud, see Add a Locally-Managed Firebox to WatchGuard Cloud and Add a Cloud-Managed Firebox to WatchGuard Cloud.

To configure AuthPoint MFA for a Firebox Cloud with Fireware v12.7.1 or higher that is not connected to WatchGuard Cloud, follow the steps in the Configure AuthPoint MFA for Firebox Cloud Mobile VPN with IKEv2 (Fireware v12.7 and Lower) section.

WatchGuard Firebox Cloud Authentication Data Flow with AuthPoint

AuthPoint communicates with various cloud-based services and service providers. This diagram shows the data flow of an MFA transaction for a Watch Guard Firebox Cloud.

Configure Security Settings for Domain Services

To configure security settings for Domain Services:

1. Log in to the Azure portal with your Microsoft Azure account credentials.
2. Click Microsoft Entra Domain Services.
3. Select your managed domain.
4. From the vertical navigation pane, select Settings > Security settings.
5. Enable the NTLM v1 Authentication option.



6. Click Save.
   The Update security settings dialog appears.
7. Click Yes.

Configure Microsoft NPS Server

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

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 Trusted interface IP address of your Firebox Cloud. In our example, the IP address is 10.0.2.5.
7. In the Shared secret and Confirm shared secret text boxes, type a shared secret key. This key is used to communicate with the Firebox Cloud.

   You must use the same shared secret key when you configure your Firebox resource in the Configure a Firebox Resource section.



8. Click OK.



9. Select Policies > 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 Microsoft Entra ID group your users belong to.
16. Click Check Names.
    Enter network credentials window appears, you must enter your credentials for an account with permissions for the Microsoft Entra Domain Services managed domain.
17. To return to the New Network Policy window, click OK three times.
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. Click Next.
24. Click Finish.

Configure AuthPoint

Before AuthPoint can receive authentication requests from the Firebox Cloud, you must:

• Add the Firebox Cloud as a Firebox resource In AuthPoint, resources are the applications and services that your users connect to. in AuthPoint.
• Add a Zero Trust 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 Firebox resource or add the Firebox resource to an existing authentication policy.
• (Optional) Add users and groups.

Configure a Firebox Resource

From the AuthPoint management UI:

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



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



4. In the Name text box, type a descriptive name for the resource.
5. From the Firebox drop-down list, select the Firebox Cloud that you want to connect to AuthPoint.

This list only shows Fireboxes and FireClusters that you have added to WatchGuard Cloud, and the device status in WatchGuard Cloud must be Connected.

6. To configure the Firebox resource to accept MS-CHAPv2 authentication requests, click the Enable MS-CHAPv2 toggle.
   Additional fields appear.
7. In the NPS Firebox 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 1812.
9. In the Timeout In Seconds text box, type 60.
10. In the Shared Secret text box, type the shared secret key that must be the same as you specified in the Configure Microsoft NPS Server section.



11. Click Save.

After you add the Firebox resource in AuthPoint, the AuthPoint authentication server on your Firebox Cloud is enabled. When you configure Mobile VPN with IKEv2 on the Firebox Cloud, you must add the AuthPoint authentication server to your Mobile VPN with IKEv2 configuration.

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.

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

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

Add a Zero Trust Authentication Policy

Zero Trust policies specify which resources users can authenticate to and which authentication methods they can use.

You must have at least one Zero Trust authentication policy that includes the Firebox resource. If you already have Zero Trust authentication policies, you do not have to create a new authentication policy. You can add this resource to your existing authentication policies.

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

To configure a Zero Trust authentication policy:

1. Go to Configure > Zero Trust. If you have a Service Provider account, you must select an account from Account Manager.
2. Click Add Policy.
3. Type a name for this policy.
4. In the Target section, from the Content drop-down list, select which groups this policy applies to. You can make multiple selections to add multiple groups.
5. In the Resources section, select the resource that you created in the Configure a Firebox Resource section. If you want this policy to apply to additional resources, select each resource this policy applies to.
6. In the Conditions section, select the conditions that apply to this policy. When you add a condition to an authentication policy, the policy applies only to user authentications that match the policy and the policy conditions. For example, if you add a time schedule to a policy, the policy only applies to user authentications that occur within that time schedule. Users who only have a policy that includes a time schedule do not get access to the resource when they authenticate outside of the allowed times (because they do not have a policy that applies, not because authentication is denied). For more information, go to About Zero Trust Conditions

   Policies that have a Network Location do apply to Firebox resources.

   1. (Optional) To create a new condition, click Add New Condition. After you create a new condition, you must still add the condition to the policy.
   2. From the Type drop-down list, select the type of condition to add to the policy.
   3. From the Name drop-down list, select which condition of the chosen type to add to the policy.
   4. To add more conditions, repeat Step 6.

      If you add conditions to a policy, we recommend that you create a second policy for the same groups and resources without the conditions. Assign a higher priority to the policy with the policy objects. For more information about priority, go to About Zero Trust Policy Precedence.

7. In the Action section, select an option to specify whether to allow or deny authentications for the resources in this policy. In our example, we want to allow authentications.
   • Allow — Allow user groups in this policy access to the resources associated with this policy.
• Deny — Deny authentications when users in the groups associated with this policy try to authenticate to the resources associated with this policy.
8. If you allow access with this policy, select the Password and Push check boxes.

   QR code authentication is not supported for Firebox resources. OTP authentication is not supported for MS-CHAPv2 Firebox resources.

9. Click Save.
   Your policy is created and added to the end of the policy list.
10. Review the order of your policies and adjust as necessary. For more information about priority, go to About Zero Trust Policy Precedence.

Sync Users to AuthPoint from Microsoft Entra ID

To sync users from Microsoft Entra ID, you must add an Azure AD external identity in the AuthPoint management UI.

In AuthPoint, Azure AD 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 Microsoft Entra ID database. They pull user information and create AuthPoint user accounts for the users that are found.

For detailed instructions to sync users from Microsoft Entra ID, see Sync Users from Microsoft Entra ID.

Configure Firebox Cloud

To configure Firebox Cloud:

1. Log in to the Azure portal with your Microsoft Azure account credentials.
2. Click Resource groups.
3. Click the Firebox Cloud resource group you created.
4. Click the NSG-<Firebox Cloud VM name>Eth0Management network security group.
5. From the vertical navigation pane, select Settings > Inbound security rules.
6. Click Add to add a new security rule.
7. From the Destination drop-down list, select IP Addresses.
8. In the Destination IP addresses/CIDR ranges text box, type the External IP address of the Firebox Cloud, including the public and private addresses.
9. In the Destination port ranges text box, type *.
10. In the Priority text box, type the number between 100 and 4096. In our example, we type 1040.
11. In the Name text box, type a name.
12. Leave the default value for all other settings.



13. Click Add.

Configure Mobile VPN with IKEv2

To configure Mobile VPN with IKEv2:

1. Log in to Fireware Web UI (https://<your Firebox IP address>:8080).
2. From the vertical navigation pane, select VPN > Mobile VPN.
3. In the IKEv2 section, click Manually Configure.



4. Select the Activate Mobile VPN with IKEv2 check box.
5. In the Firebox Addresses section, click Edit.



6. From the Type drop-down list, select Firebox-Generated Certificate.
7. In the Domain Name or IP Address section, type the External IP address of the Firebox.



8. Click Add.
9. Click OK.
10. In the Networking section, select Force all client traffic through the tunnel.

    You can also select Specify allowed resources. For more information about IKEv2 Mobile VPN, see Mobile VPN with IKEv2.

11. Select the Authentication tab.
12. In the Authentication Server section, from the drop-down list, select AuthPoint, and click Add.
13. To make AuthPoint the default authentication server, in the Authentication Server list, select AuthPoint and click Move Up to move it to the top of the list.
    Mobile VPN with IKEv2 uses the default authentication server unless a user specifies an authentication server on the Mobile VPN with IKEv2 client.
    
14. In the Users and Groups section, from the Create new drop-down list, select AuthPoint.
15. From the adjacent drop-down list, select Group.

    You can add a user or a group. In our example, we add a group.

16. Click Add.
    The Add User or Group window appears.
17. For Type, select Group.
18. In the Name text box, type a name for the group. The name of this group must match the group name in AuthPoint.

    If you add a user, the name of the user must match the name of the Microsoft Entra ID user.

19. From the Authentication Server drop-down list, select AuthPoint.



20. Click Save.
    Your new group added to the Users and Groups list.



21. Click Save to save your configuration.
22. From the vertical navigation pane, select VPN > Mobile VPN.
23. In the IKEv2 section, click Client Profile.
    The Client Profiles and Instructions page opens.
24. Click Download.
25. Extract the .TGZ file to your Windows 10 computer and find the Windows_8.1_10_11 folder.
26. Run the WG IKEv2.bat file.
    The IKEv2 VPN will be created and configured automatically on your Windows 10 computer.

Test the Integration

To test the integration of AuthPoint and the configuration of your Mobile VPN with IKEv2, you authenticate with a mobile token on your mobile device. For Firebox 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, open the Windows menu and select Settings.
2. Select Network & Internet > VPN.
3. Select your VPN connection and click Connect.
4. Type your username and password.
5. Approve the authentication request that is sent to your mobile device.
   The VPN connects successfully.
   

The steps to configure AuthPoint and your Firebox Cloud are different based on the version of Fireware that you have. Complete the steps in this section to configure AuthPoint MFA for Microsoft Entra ID users that use Mobile VPN with IKEv2 with Fireware v12.7 and lower or if you have a Firebox Cloud with Fireware 12.7.1 or higher but not connected to WatchGuard Cloud.

WatchGuard Firebox Cloud Authentication Data Flow with AuthPoint.

AuthPoint communicates with various cloud-based services and service providers with the RADIUS protocol. This diagram shows the data flow of an MFA transaction for a WatchGuard Firebox Cloud.

Configure Security Settings for Domain Services

To configure security settings for Domain Services:

1. Log in to the Azure portal with your Microsoft Azure account credentials.
2. Click Microsoft Entra Domain Services.
3. Select your managed domain.
4. From the vertical navigation pane, select Settings > Security settings.
5. Enable the NTLM v1 Authentication option.



6. Click Save.
   The Update security settings dialog appears.
7. Click Yes.

Configure Microsoft NPS Server

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

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 10.0.2.5.
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 Firebox Cloud in the Configure RADIUS Authentication Server section and Add a RADIUS Client Resource in AuthPoint section.



8. Click OK.



9. Select Policies > 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 Microsoft Entra ID group your users belong to.
16. Click Check Names.
    Enter network credentials window appears, you must enter your credentials for an account with permissions for the Microsoft Entra Domain Services managed domain.
17. To return to the New Network Policy window, click OK three times.
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–28.
24. From the Attributes list, select Filter-Id, then 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 Microsoft Entra ID group your users belong to.



27. Click OK twice.
28. Click Close.



29. Click Next.
30. Click Finish.

Configure the Firebox Cloud

Before you configure the WatchGuard Firebox Cloud, you must deploy it on Azure. For detailed steps, see Deploy Firebox Cloud on Microsoft Azure.

To configure the Firebox Cloud, complete these steps:

1. Configure Security Rule for Firebox Cloud
2. Configure RADIUS Authentication Server
3. Configure Mobile VPN with IKEv2

Configure Security Rule for Firebox Cloud

To configure security rule for Firebox Cloud:

1. Log in to the Azure portal with your Microsoft Azure account credentials.
2. Click Resource groups.
3. Click the Firebox Cloud resource group you created.
4. Click the NSG-<Firebox Cloud VM name>Eth0Management network security group.
5. From the vertical navigation pane, select Settings > Inbound security rules.
6. Click Add to add a new security rule.
7. From the Destination drop-down list, select IP Addresses.
8. In the Destination IP addresses/CIDR ranges text box, type the External IP address of the Firebox Cloud, including the public and private addresses.
9. In the Destination port ranges text box, type *.
10. In the Priority text box, type the number between 100 and 4096. In our example, we type 1040.
11. In the Name text box, type a name.
12. Leave the default value for all other settings.



13. Click Add.

Configure RADIUS Authentication Server

When a user authenticates with AuthPoint MFA, AuthPoint does not send a response to the Firebox until the user approves the push notification that is sent to them or until the push authentication expires.

When you configure the RADIUS authentication server, the timeout value must be greater than the combined push timeout The push timeout is the amount of time before a push authentication expires. for AuthPoint (60 seconds) and NPS (30 seconds). With the default settings on the RADIUS authentication server, if a user does not approve the push notification that is sent to them within 30 seconds (3 tries, 10 seconds each), the Firebox will fail over to another server, even though the current server is not down.

To configure the RADIUS authentication:

1. Log in to Fireware Web UI (https://<your Firebox IP address>:8080).
2. From the vertical navigation pane, select Authentication > Servers.
   The Authentication Servers page opens.



3. From the Authentication Servers list, click RADIUS.
   The RADIUS page opens.
4. Click Add.
   The Add page opens.
5. In the Domain Name text box, type the domain name for this RADIUS server. Users must specify this domain name on the user login page. You cannot change the domain name after you save the settings.
6. In the Primary Server Settings section, select the Enable RADIUS Server check box.
7. In the IP Address text box, type the IP address of the RADIUS server (AuthPoint Gateway).
8. In the Port text box, leave the default port setting of 1812. This is the default port used for communication with the RADIUS server (AuthPoint Gateway).

   If you already have a RADIUS server installed that uses port 1812, or if NPS and the Gateway are installed on the same server, you must use a different port for the AuthPoint Gateway.

9. In the Shared Secret and Confirm Secret text boxes, type the shared secret key that you specified in the Configure Security Rule for Firebox Cloud section. This is the password that the RADIUS server (AuthPoint Gateway) and the RADIUS client (Firebox Cloud) will use to communicate.
10. In the Timeout text box, type 90.
11. Leave the default value for Group Attribute.



12. Scroll down to the bottom of the page and click Save.

Configure Mobile VPN with IKEv2

To configure Mobile VPN with IKEv2:

1. From the vertical navigation pane, select VPN > Mobile VPN.
2. In the IKEv2 section, click Manually Configure.



3. Select the Activate Mobile VPN with IKEv2 check box.
4. In the Firebox Addresses section, click Edit.



5. From the Type drop-down list, select Firebox-Generated Certificate.
6. In the Domain Name or IP Address section, type the External IP address of the Firebox.



7. Click Add.
8. Click OK.
9. In the Networking section, select Force all client traffic through the tunnel.

   You can also select Specify allowed resources. For more information about IKEv2 Mobile VPN, see Mobile VPN with IKEv2.

10. Select the Authentication tab.
11. In the Authentication Server section, from the drop-down list, select the RADIUS authentication server you created, and click Add.
12. To make the RADIUS authentication server the default authentication server, in the Authentication Server list, select the RADIUS authentication server and click Move Up to move it to the top of the list.
    Mobile VPN with IKEv2 uses the default authentication server unless a user specifies an authentication server on the Mobile VPN with IKEv2 client.
    
13. In the Users and Groups section, from the Create new drop-down list, select the RADIUS authentication server you created.
14. From the adjacent drop-down list, select Group.

    You can add a user or a group. In our example, we add a group.

15. Click Add.
    The Add User or Group dialog box appears.
16. For Type, select Group.
17. In the Name text box, type a name for the group. The name of this group must match the Microsoft Entra ID group your users belong to.

    If you add a user, the name of the user must match the name of the Microsoft Entra ID user.

18. From the Authentication Server drop-down list, select the RADIUS authentication server you created.



19. Click Save.
    Your new group added to the Users and Groups list.



20. Click Save to save your configuration.
21. From the vertical navigation pane, select VPN > Mobile VPN.
22. In the IKEv2 section, click Client Profile.
    The Client Profiles and Instructions page opens.
23. Click Download.
24. Extract the .TGZ file to your Windows 10 computer and find the Windows_8.1_10_11 folder.
25. Run the WG IKEv2.bat file.
    The IKEv2 VPN will be created and configured automatically on your Windows 10 computer.

Configure AuthPoint

Before AuthPoint can receive authentication requests from the Firebox Cloud, you must:

• Add the Firebox Cloud as a RADIUS client resource In AuthPoint, resources are the applications and services that your users connect to. in AuthPoint.
• Add a Zero Trust 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 Firebox RADIUS client resource or add the Firebox RADIUS client resource to an existing authentication policy.
• Bind the Firebox 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. On the RADIUS page, in the Name text box, type a name for this 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. For Firebox, this is usually the Trusted IP address of your Firebox.
5. Leave the default value in the Value sent for RADIUS attribute 11 (Filter-Id) drop-down list. This setting is not supported for MS-CHAPv2 authentication requests made by Microsoft Entra ID users.
6. In the Shared Secret text box, type the shared secret key that you specified in the Configure Security Rule for Firebox Cloud and Configure Microsoft NPS Server section. This is the password that the RADIUS server (AuthPoint Gateway) and the RADIUS client (Firebox Cloud) will use to communicate.
7. To configure the RADIUS client resource to accept MS-CHAPv2 authentication requests, select the Enable MS-CHAPv2 check box.
   Additional fields appear.
8. In the NPS RADIUS Server trusted IP or FQDN text box, type the IP address of your 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 30.



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

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

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

Add a Zero Trust Authentication Policy

Zero Trust policies specify which resources users can authenticate to and which authentication methods they can use.

You must have at least one Zero Trust authentication policy that includes the Firebox RADIUS client resource. If you already have Zero Trust authentication policies, you do not have to create a new authentication policy. You can add this resource to your existing authentication policies.

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

To configure a Zero Trust authentication policy:

1. Go to Configure > Zero Trust. If you have a Service Provider account, you must select an account from Account Manager.
2. Click Add Policy.
3. Type a name for this policy.
4. In the Target section, from the Content drop-down list, select which groups this policy applies to. You can make multiple selections to add multiple groups.
5. In the Resources section, select the AuthPoint resources this policy applies to.
6. In the Conditions section, select the conditions that apply to this policy. When you add a condition to an authentication policy, the policy applies only to user authentications that match the policy and the policy conditions. For example, if you add a time schedule to a policy, the policy only applies to user authentications that occur within that time schedule. Users who only have a policy that includes a time schedule do not get access to the resource when they authenticate outside of the allowed times (because they do not have a policy that applies, not because authentication is denied). For more information, go to About Zero Trust Conditions

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

   1. (Optional) To create a new condition, click Add New Condition. After you create a new condition, you must still add the condition to the policy.
   2. From the Type drop-down list, select the type of condition to add to the policy.
   3. From the Name drop-down list, select which condition of the chosen type to add to the policy.
   4. To add more conditions, repeat Step 6.

      If you add conditions to a policy, we recommend that you create a second policy for the same groups and resources without the conditions. Assign a higher priority to the policy with the policy objects. For more information about priority, go to About Zero Trust Policy Precedence.

7. In the Action section, select an option to specify whether to allow or deny authentications for the resources in this policy. In our example, we want to allow authentications.
   • Allow — Allow user groups in this policy access to the resources associated with this policy.
• Deny — Deny authentications when users in the groups associated with this policy try to authenticate to the resources associated with this policy.
8. If you allow access with this policy, select the Password and Push check boxes.

   QR code authentication is not supported for RADIUS client resources. OTP authentication is not supported for RADIUS client resources with MS-CHAPv2 enabled.

9. Click Save.
   Your policy is created and added to the end of the policy list.
10. Review the order of your policies and adjust as necessary. For more information about priority, go to About Zero Trust Policy Precedence.

Bind the RADIUS Resource to a Gateway

To use RADIUS authentication with AuthPoint, you must have the AuthPoint Gateway installed on Azure 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 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 Microsoft Entra ID

To sync users from Microsoft Entra ID, you must add an Azure AD external identity in the AuthPoint management UI.

In AuthPoint, Azure AD 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 Microsoft Entra ID database. They pull user information and create AuthPoint user accounts for the users that are found.

For detailed instructions to sync users from Microsoft Entra ID, see Sync Users from Microsoft Entra ID.

Test the Integration

To test the integration of AuthPoint and the configuration of your Mobile VPN with IKEv2, you 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. Select your VPN connection and click Connect.
5. Type your username and password.
6. Approve the authentication request that is sent to your mobile device.
   The VPN connects successfully.