Description This article demonstrates how to configure a dial-up IPsec
VPN using IKEv2 and Multi-Factor Authentication (MFA) with Duo
authentication proxy. Scope FortiOS v6.2.4 and later, dial-up IKEv2 VPN.
Solution This article refers to non-SSO aut...
Description This article provides an overview of guides and resources
for User and Multi-Factor authentication in FortiOS IKEv2 Dialup IPsec
VPN. Scope FortiOS v7 and later. Solution Determine the User source and
required MFA method(s) and refer to t...
Description This article demonstrates an example configuration allowing
Active Directory users to connect to FortiGate IKEv2 VPN with FortiToken
hosted on FortiAuthenticator. Scope FortiGate, FortiAuthenticator,
FortiClient, FortiToken, IKEv2 Solutio...
Description This article describes a known issue preventing the use of
computer certificates for authenticating to IPsec VPN after upgrading to
FortiClient Windows v7.4.4. Scope FortiClient Windows v7.4.4. Solution
FortiClient can access certificates...
Description This article describes an unsupported configuration that may
cause VPN connections to fail after upgrade to FortiOS v7.4.9. Scope
FortiOS v7.4.9, v7.6.3 and later. Solution If Azure AD auto-connect is
enabled on the FortiClient but not co...
Thank you, this appears to match known issue 1205084 . It's scheduled
for fix in FCT v7.4.5.
https://docs.fortinet.com/document/forticlient/7.4.4/windows-release-notes/573433/new-known-issues."Re-importing
the certificate" is the listed workaround fo...
If it works for SSL VPN, this suggests FortiClient itself has the
required permissions to access the cert. For IPsec, ensure
is enabled for the VPN connection profile. It is
disabled by
default.https://docs.fortinet.com/document/forticlient/7.4.4/xm...
Thread is old, but to avoid the use of fnsysctl (which loses permissions
to read /etc/upd.dat in later firmware versions), use "diagnose test
update info" to retrieve the FortiCare account FortiGate believes it is
registered to.diagnose test update i...
Sometimes, useful info you can only find in one place is wrong! v7.2.11
was released yesterday and v7.0.17->v7.2.11->v7.4.7 is a supported
upgrade path despite breaking the rule of thumb I just gave (v7.2.11
released 2025-02-12, v7.4.7 released 2025-...
