Multi-Factor Authentication (2FA/MFA) for Fortinet FortiGate IPSec VPN

Overview of MFA for Fortinet FortiGate IPSec VPN using LDAP(S)

This documentation describes how to integrate Rublon MFA with Fortinet FortiGate IPSec VPN using the LDAP(S) protocol to enable multi-factor authentication for VPN connections.

Demo Video

Supported Authentication Methods

Authentication Method	Supported	Comments
Mobile Push	✔	N/A
FIDO	–	N/A
Passcode	✔	N/A
SMS Passcode	–	N/A
SMS Link	✔	N/A
Phone Call	✔	N/A
QR Code	–	N/A
Email Link	✔	N/A
YubiKey OTP	✔	N/A
RFID	–	N/A

Before You Start Configuring MFA for Fortinet FortiGate IPSec VPN using LDAP(S)

Before configuring Rublon MFA for Fortinet FortiGate VPN:

Ensure you have prepared all required components.
Create an application in the Rublon Admin Console.
Install the Rublon Authenticator mobile app.

Required Components

1. User Identity Provider (IdP) – You need an external Identity Provider, such as Microsoft Active Directory, OpenLDAP, or FreeRADIUS.

2. Rublon Authentication Proxy – Install the Rublon Authentication Proxy if you have not already and configure the Rublon Authentication Proxy as an LDAP proxy.

3. Fortinet Fortigate – Properly installed and configured.

Create an Application in the Rublon Admin Console

1. Sign up for the Rublon Admin Console. Here’s how.

2. In the Rublon Admin Console, go to the Applications tab and click Add Application.

3. Enter a name for your application (e.g., Fortinet FortiGate IPSec VPN) and then set the type to Rublon Authentication Proxy.

4. Click Save to add the new application in the Rublon Admin Console.

5. Copy and save the values of the System Token and Secret Key. You are going to need these values later.

Install Rublon Authenticator

Some end-users may use the Rublon Authenticator mobile app. So, as a person configuring MFA for Fortinet Fortigate VPN, we highly recommend you install the Rublon Authenticator mobile app, too. Thanks to that, you will be able to test MFA for Fortinet FortiGate via Mobile Push.

Download the Rublon Authenticator for:

Configuring Multi-Factor Authentication (MFA) for Fortinet FortiGate IPSec VPN using LDAP(S)

Follow the steps in this section to enable Rublon 2FA in your Fortinet FortiGate IPSec VPN.

Add Rublon Authentication Proxy as LDAP Server in Fortinet FortiGate

1. Log in to the Fortinet FortiGate administrator panel.

2. Click the User & Authentication section on the left to expand it and click LDAP Servers.

3. Click the Create New button to add your Rublon Authentication Proxy.

4. Fill in the form and click OK to add your new server. Refer to the following image and table.

Name	Set a name for your new server, e.g. Rublon Authentication Proxy.
Server IP/Name	Enter the IP address or FQDN of your Rublon Authentication Proxy.
Server Port	Enter the port of your Rublon Authentication Proxy (by default, 389 for LDAP; 636 for LDAPS).
Common Name Identifier	cn
Distinguished Name	Base DN for the local domain or a specific OU from the local domain – written in LDAP notation (e.g., DC=rublondemo,DC=local).
Exchange Server	Uncheck.
Bind Type	Regular
Username	Enter the Bind DN of a user who has Read rights in your LDAP(S) server.
Password	Enter the password of the user defined by Bind DN.
Secure Connection	Check if using LDAPS.

5. You can now check your setup using the Test Connectivity and Test User Credentials buttons. Clicking Test Connectivity will check the connection from the FortiGate to the Rublon Authentication Proxy while clicking Connection Status will show if the connection was successful or not.

Configure a User Group

1. Click the User & Authentication section on the left to expand it and click User Groups.

2. If you already have an existing user group, double-click the name of the group to edit its settings. If you haven’t created a user group yet, click Create New to create one. Enter the following information in the New User Group form:

Name	Rublon
Type	Firewall

3. Click the Add button in the Remote Groups section. In Add Group Match, select the Rublon Authentication Proxy remote server. You do not have to specify a group. Click OK to add the remote server.

4. Click OK to save the user group settings.

5. If you are using an LDAP server (e.g., Active Directory) in your Rublon Authentication Proxy, adding the user group via the GUI might not be enough. You might have to complete the following steps to map to the DN of an AD group using CLI.

After saving the group settings, click Edit, then click Edit in CLI, and then execute the following commands:

set member NAME_OF_THE_SERVER_FROM_LDAP_SERVERS
config match
edit 1
set server-name NAME_OF_THE_SERVER_FROM_LDAP_SERVERS
set group-name DN_OF_THE_GROUP_FROM_AD
next
end
end

You can now close the console and refresh the page. You should now see your mapping to the DN of an AD group.

Note

If a user has two accounts with the same name in the FortiGate system – one is a user account for VPN connections and the other is an administrative account (defined in System → Administrators) – and both accounts authenticate through an external Identity Provider (IdP), then after deploying the Rublon Authentication Proxy, switch the administrative account to local authentication (System → Administrators → Edit Administrator → set Type to Local User).

Retaining the admin account’s authentication through the external Identity Provider will result in the user’s VPN connections not requiring a second factor of authentication. This happens because FortiGate sees two accounts with the same username in the same source. If the admin account (using the same username) is also configured in the external IdP and does not require MFA, FortiGate will finalize the login as soon as it receives a positive response for that account—before the Rublon Auth Proxy authentication process completes (which takes longer, for example because it waits for the user’s approval in the Rublon Authenticator app). Switching the admin account to “Local User” ensures that FortiGate no longer searches for an alternate identity source with the same username, thereby always requiring a second factor of authentication for VPN connections.

Configure Firewall Policy and Mapping

1. Configure the IPSec VPN Tunnel if you have not already.

2. Click Policy & Objects on the left to expand it and select IPV4 Policy.

Note: In some cases, there will be a Firewall Policy option instead of an IPV4 Policy.

3. Create or edit the policy related to your IPSec-VPN interface.

4. In Source, add the address space (e.g., IPSECVPN_TUNNEL-ADDR1) and the group (Rublon if you followed this document closely) you created before

5. Click OK to save the changes.

6. Click VPN on the left to expand it and select IPSec-VPN Settings.

7. Navigate to the Authentication/Portal Mapping section.

8. Create New or Edit existing mapping to grant access to the group you created before. Unless your requirements are different, allow full-access.

9. Click OK and then Apply to save the changes.

Configure Timeout and Additional Options

The default timeout in the Fortinet appliance is 5 seconds, which is far too short for anything other than Passcode authentication. You have to increase the timeout in the Fortinet command line interface. We recommend you increase the timeout to at least 180 seconds.

1. Connect to the appliance command-line interface (CLI). If you need more information, refer to the documentation that came with your Fortinet device.

2. Execute the following commands:

config system global
set remoteauthtimeout 60
set ldapconntimeout 60000
end

remoteauthtimeout: This time is specified in seconds.
ldapconntimeout: This time is specified in milliseconds.

Configure IPSec

1. In the Fortinet FortiGate administrator panel, go to VPN → VPN Tunnels and select your IPSec VPN profile. Then select Edit.

2. In the Tunnel Settings tab, navigate to the Authentication section and fill out the fields. Refer to the following image and table.

Method	Select Pre‑shared Key or Signature, depending on your IPSec configuration. These are methods of authenticating the connection between the client and the server. The first uses a shared password, while the second relies on a certificate. More information: Pre-shared key vs digital certificates
IKE	Version 1
Mode	Main (ID Protection)
Accepted peer ID	Any peer ID
XAuth	Auto server
User Group	Specify and select the group you have created in Configure a User Group.

3. Leave all other fields at their default values or adjust them according to your needs, and then select OK to save your configuration.

Log in to FortiGate IPSec VPN using MFA for Fortinet FortiGate IPSec VPN Integrated Via RADIUS

Rublon MFA for FortiGate IPSec VPN requires the use of the FortiClient VPN.

In this example, Mobile Push has been set as the second factor in Rublon Authentication Proxy configuration (AUTH_METHOD was set to push).

1. Open the FortiClient VPN and create a new IPSec VPN connection.

2. Select IPSec VPN and then set the following settings:

Enter the IP in the Remote Gateway.
Specify the Authentication Method.
Expand Advanced Settings → VPN Settings and set the following:
- IKE: Version 1
- Mode: Main
- Address Assignment: Mode Config
Expand Advanced Settings → Phase 1 and set the following:
- IKE Proposal: AES128/SHA1; AES256/SHA256
- DH Group: 20 i 21
- Key Life: 86400
Expand Advanced Settings → Phase 2 and set the following:
- IKE Proposal: AES128/SHA1; AES256/SHA256
- Key Life: 43200
- DH Group: 20
Select Save.