Skip to main content

How do I configure my F5® FirePass SSL VPN device for use with ESET Secure Authentication? - Kennisbank / ESET Secure Authentication - ESET Tech Center

How do I configure my F5® FirePass SSL VPN device for use with ESET Secure Authentication?

Authors list


This article describes how to configure a F5® FirePass SSL VPN device to authenticate users against an ESA Server. Before proceeding, verify that you've installed the RADIUS Server component of ESET Secure Authentication and can access the RADIUS service that allows external systems to authenticate users.

Before your F5® FirePass SSL VPN device can use the ESA Server to authenticate users via RADIUS, it must be set up as a RADIUS client on the ESA Server. Next, your server running the ESA RADIUS service must be setup as a RADIUS Server on the F5® FirePass SSL VPN device. Once these configurations have been specified, you can start logging into your F5® FirePass SSL VPN device using ESA OTPs.


This integration guide utilizes VPN does not validate AD user name and password VPN type for this particular VPN appliance. If you wish to utilize other VPN type, refer to generic description of VPN typesand verify with the vendor if the VPN appliance supports it.

Step I - RADIUS client configuration

To allow the F5® FirePass SSL VPN device to communicate with your ESA Server, you must configure the F5® FirePass SSL VPN device as a RADIUS client on your ESA Server:

  1. Launch the ESA Management Console (found under Administrative Tools).
  2. Navigate to RADIUS Servers and locate the hostname of the server running the ESA RADIUS service.
  3. Right-click the hostname and select Add Client from the context menu.
  4. Configure a RADIUS client (see Figure 1-1).
  5. Click OK - you will be prompted to restart the RADIUS Service, do so from the Services control panel.

Configuring your RADIUS client

  • To prevent locking any existing, non-2FA enabled AD users out of your VPN we recommend that you allow Active Directory passwords without OTPs during the transitioning phase. It is also recommended that you limit VPN access to a security group (for example VPNusers).
  • Make sure that the check box next to Mobile Application is selected.

Figure 1-1

ESA has now been configured to communicate with the F5® FirePass SSL VPN device. You must now configure the F5® FirePass SSL VPN device to communicate with the ESA Server.

Step II - Configure your F5® FirePass SSL device

Follow the steps below:

  1. Login to your F5® FirePass SSL administrative interface.
  2. Click Users.
  3. Click Groups → Master Groups → Create New Group (or modify an existing group)
  4. Set the following parameters to the values shown below:
    1. Group Name: ESA
    2. Users in group: external
    3. Authentication method: RADIUS 
  5. Click Create.
  6. Navigate to the Authentication tab for your new group and set the following parameters to the values shown below:
    1. Timeout30
    2. Retries: 2
    3. Server: The IP address of your ESA RADIUS server
    4. Port: 1812
    5. Shared Secret: The shared secret from your RADIUS server configuration (see Figure 1-1)
    6. Confirm Shared Secret: Repeat the shared secret
  7. Click Save Settings

Step III - Test the connection

To test the newly configured connection:

  1. Navigate to the URL that you normally use for SSL VPN logins with your F5® FirePass SSL VPN appliance.
  2. Enter the credentials of your test user. Ensure that you are using an account with Mobile Application 2FA using ESA enabled. When prompted for a password, append the OTP generated by the Mobile Application to your AD password. For example, if the user has an AD password of Esa123 and an OTP of 999111, you should type Esa123999111.



If you are unable to authenticate via the ESA RADIUS server, make sure that you have performed the following steps:

  1. Run a smoke test against your RADIUS server, as per the Verifying ESA RADIUS Functionality.
  2. If no faults were fixed and you are still unable to connect, revert to an existing sign-in configuration that does not use 2FA and verify that you are able to connect.
  3. If you are able to connect using the old settings, restore the new settings and verify that there is no firewall blocking UDP 1812 between you VPN device and your RADIUS server.
  4. If you are still unable to connect, contact ESET technical support.

Reactie toevoegen

Please log in or register to submit a comment.

Need a password reminder?