ESET Secure Authentication – Table of Contents

RADIUS Configuration

To configure 2FA for your VPN, add your VPN appliance as a RADIUS client:

1.In the ESA Web Console, navigate to Components > RADIUS, select a RADIUS server, and click Create Client.

2.In the Basic Settings section:

a.Give the RADIUS client a memorable name for easy reference.

b.Configure the IP Address and Shared Secret for the Client so that they correspond to the configuration of your VPN appliance. The IP address is the internal IP address of your appliance. If your appliance communicates via IPv6, use that IP address along with the related scope ID (interface ID).

c.The shared secret is the RADIUS shared secret for the external authenticator you will configure on your appliance.

3.In the Authentication section:

a.Select the Client Type.

b.Select the desired authentication method. The optimal authentication method depends on your VPN appliance make and model. For more details, see ESA VPN integration guidelines Knowledgebase article.

c.Optionally, you can allow any non-2FA users to use the VPN.


Note

Non-2FA users

Allowing non-2FA users to log in to the VPN without restricting access to a security group will allow all users in the domain to log in using the VPN. Using this configuration is not recommended.

Suppose an ESA RADIUS client is configured to allow Non-2FA users to log in using their generic credentials. If self-enrollment with any default authentication type is enabled, all users will be requested to provide 2FA or MRK to authenticate.

RADIUS client authentication overview

4.In the Users section, from the Realm selection box, select Current AD domain or Current AD domain and domains in trust to have the realm (domain) of the user be automatically registered when the user authenticates for the first time using VPN and 2FA. Alternatively, select a specific realm from the selection box to have all users be registered to the same realm.

5.If your RADIUS client supports the Message-Authenticator attribute, select Require Message-Authenticator attribute to mitigate potential security risks and vulnerabilities (CVE-2024-3596)

6.If your VPN client requires additional RADIUS attributes to be sent by ESA RADIUS, in the Attributes section, click Add Attribute to configure them. Remember to select the correct Value Type for your attribute so the RADIUS component can parse it.

7.When you are finished making changes, click Save.

8.Restart the RADIUS server.

a.Locate the ESA RADIUS Service in the Windows Services (under Control Panel > Administrative Tools > View Local Services).

b.Right-click the ESA Radius Service and select Restart from the context menu.


Note

Push Authentication

If the Mobile Application Push authentication method is enabled, set the authentication expiration time of your VPN server to more than 2.5 minutes.

Client Type options


Note

For more details, see ESA VPN integration guidelines Knowledgebase article.

Client does not validate user name and password

Customers who use Active Directory synchronization can use this option for RADIUS clients that do not validate the first factor. The RADIUS server needs access to Active Directory to support the password verification. The supported VPN solutions include FortiGate VPN, WatchGuard VPN, and Palo Alto GlobalProtect VPN.

You can also use these modes:

•Client does not validate user name and password-use Access-Challenge—Use this option if your VPN server contacts only ESA RADIUS to verify both factors (username and password as the first factor, and OTP as the second factor), but the authentication consists of two steps. The following RADIUS clients support the RADIUS Access-Challenge feature:

oPulse Secure (VPN)

oLinux PAM module

The Access-Challenge feature in ESA RADIUS supports only the PAP protocol. Therefore, the Microsoft RRAS RADIUS client using MS-CHAPv2 should not be used with this mode.

•Client does not validate user name and password-avoid compound—Use this option only if your VPN server uses MS-CHAPv2 (where a compound password is not supported), and it contacts ESA RADIUS to verify both factors (username and password as the first factor, and OTP as the second factor).

Client validates user name and password

Use this option if the client (for example, a VPN server) validates the primary password (for example, by contacting Active Directory directly or by using some local user database) and contacts ESA RADIUS to validate the second factor. Such clients usually have a separate configuration option for the second factor, and they provide two password fields for the user-primary password and second factor.

See ESA Web Console to learn what the user will type to the second-factor field for the available authentication options.

Client validates user name and password-use Access-Challenge

Use this option if the client (for example, a VPN server) validates the primary password (for example, by contacting Active Directory directly or by using some local user database) and contacts ESA RADIUS to validate the second factor. With this option, ESA RADIUS does not validate the first factor, only the second factor. If needed, it prompts for the second factor.

See ESA Web Console to learn what the user will type to the second-factor field for the available authentication options.

Only some clients support this mechanism (Access-Challenge response), and they require the correct configuration to use this mechanism. They usually provide two steps for the user; First, the user types their username and primary password. In the second step, the user will type the second factor if needed.