How to Configure FortiToken Two-Factor Authentication with LDAP for SSL VPN
A network administrator wants to implement two-factor authentication for SSL VPN users using FortiToken. The users are already authenticated against an LDAP server. Which configuration step is required to enforce two-factor authentication?
Quick Answer
The answer is to create a user group that uses LDAP as the authentication server and enable FortiToken two-factor authentication in the group settings. This configuration is required because FortiGate treats two-factor authentication as a group-level policy: the LDAP server handles the primary password verification, while the FortiToken code provides the second factor, ensuring both credentials are validated before granting SSL VPN access. On the Fortinet NSE 4 Network Security Professional NSE4 exam, this question tests your understanding of how to integrate FortiToken two-factor authentication with an existing LDAP directory for SSL VPN, a common enterprise scenario. A frequent trap is assuming you can enable FortiToken directly on the LDAP server or user object, but FortiGate requires the group object to bind the two authentication sources together. Memory tip: think of the user group as the “bridge” that connects your LDAP password to the FortiToken code—without the group, the bridge collapses.
⚠ Common exam trap
Many exam-takers think two-factor authentication can be enabled directly on the SSL VPN portal or by creating a local user with a token, but FortiGate requires the token to be associated with a user group that references the external authentication server.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a user group that uses LDAP as the authentication server and enable FortiToken two-factor authentication in the group settings
FortiGate requires a user group to combine LDAP authentication with FortiToken two-factor authentication. By creating a user group that uses LDAP as the authentication server and enabling FortiToken in the group settings, the FortiGate will first authenticate the user against LDAP and then prompt for a FortiToken code as the second factor. This is the standard method to enforce two-factor authentication for SSL VPN users without creating duplicate local users.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a local user with the same username as the LDAP user and assign a FortiToken to that local user
Why it's wrong here
This would create a separate local user, not leverage the LDAP authentication. The user would authenticate locally, not against LDAP.
- ✓
Create a user group that uses LDAP as the authentication server and enable FortiToken two-factor authentication in the group settings
Why this is correct
Correct. The user group authenticates against LDAP and then requires a FortiToken for two-factor.
- ✗
Configure the SSL VPN portal to require FortiToken and set the authentication server to LDAP
Why it's wrong here
The SSL VPN portal does not have an authentication server setting; it uses the firewall policy's authentication.
- ✗
Set the SSL VPN authentication method to 'certificate' and use FortiToken as second factor
Why it's wrong here
Certificate authentication is a different primary method; it does not integrate with FortiToken in the same manner.
Quick reference
VPN Protocol Comparison
| Protocol | Port | Encryption | Authentication | Use Case |
|---|---|---|---|---|
| IKEv2 / IPsec | UDP 500 / 4500 | AES-256 | Certificates / PSK | Site-to-site & remote access |
| SSL / TLS VPN | TCP 443 | TLS 1.3 | Certificates / MFA | Clientless remote access |
| L2TP / IPsec | UDP 1701 | AES (IPsec) | PSK / Certificates | Legacy remote access |
| WireGuard | UDP 51820 | ChaCha20 | Public keys | Modern high-performance VPN |
| PPTP | TCP 1723 | MPPE (weak) | MS-CHAPv2 | Legacy — avoid in production |
PPTP is considered insecure. IKEv2/IPsec and SSL VPN are the current recommended options.
Go deeper
Related to this question
About these practice questions
This NSE4 question is part of Courseiva's 282-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on NSE4
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A FortiGate administrator wants to enforce two-factor authentication for SSL VPN users. The organization uses FortiToken mobile tokens. What must be configured on the FortiGate to enable FortiToken authentication?
easy- ✓ A.In the user group configuration, enable two-factor authentication and select 'FortiToken'
- B.Configure a RADIUS server to forward FortiToken requests
- C.Set the SSL VPN portal to require client certificates
- D.Install the FortiToken mobile app on the FortiGate
Why A: FortiGate natively supports FortiToken two-factor authentication directly in the user group configuration. By enabling two-factor authentication and selecting 'FortiToken' within the user group settings, the FortiGate will prompt SSL VPN users for both their password and a one-time password generated by the FortiToken mobile app, without requiring any external server.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This NSE4 practice question is part of Courseiva's free Fortinet certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the NSE4 exam.