Hello,
Seems we are forced to move from SSL to IPSEC VPN so we are actually trying it on our FTG901G v7.4.9
Our authentication is direct from the fortigate to Active Directory (ldaps)
It is working since we activated EAP-TTLS thank's to this trick : https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-enable-EAP-TTLS-for-IPSec-IKEv2-tun...
BUT, it is not working when we add a FortiToken on the account
I saw on this page that 2FA is supported from client v7.4.4 with IKEv2 ldap users : https://community.fortinet.com/t5/FortiGate/Technical-Tip-Overview-of-compatible-IKE-versions-user/t...
The little stars lead us to this Technical Tip and this Special Notice which explain that there is no free version of the 7.4.4 Forticlient, BUT the 7.4.3 free VPN-only agent is supposed to do the same job :
https://docs.fortinet.com/document/forticlient/7.4.4/windows-release-notes/683433/special-notices
I've read a lot of kb, tips and fortidocs but I'm still not sure to understand : are our FortiToken supposed to work in our situation ? :
VPN IPSec IKEv2 + ldaps auth (eap-ttls) + free VPN-only agent
hi,
have a look at https://community.fortinet.com/t5/FortiGate/Technical-Tip-Overview-of-compatible-IKE-versions-user/t...
how is the FortiToken assigned to the user ? locally on the FGT , on FortiAuth or using FortiIdentity Cloud ?
| User | Count |
|---|---|
| 2878 | |
| 1446 | |
| 843 | |
| 822 | |
| 455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.