FortiClient
FortiClient proactively defends against advanced attacks. Its tight integration with the Security Fabric enables policy-based automation to contain threats and control outbreaks. FortiClient is compatible with Fabric-Ready partners to further strengthen enterprises’ security posture.
btan
Staff & Editor
Staff & Editor
Article Id 387374
Description This article describes how to resolve the issue when connecting to a certificate-based authentication SSL VPN or IPsec VPN with Smart Card as Multifactor authentication (MFA), FortiClient does not prompt for MFA.
Scope FortiClient v7.0.9+, v7.2, v7.4.
Solution

After upgrading FortiClient to versions 7.0.9, 7.2.x, or 7.4.x, when connecting to certificate-based authentication, SSL VP,N or IPsec VPN with Smart Card as Multifactor authentication (MFA), FortiClient does not prompt for MFA. This results in the VPN stopping at 40% and not being connected:


apr-kb2-1.PNG

 

Checking in FortiClient Notification, it shows 'Permission denied. (-455)' error:

 

apr-kb2-2.PNG

 

To resolve this, go to EMS -> Endpoint Profile -> Remote Access -> (select the profile) -> Edit -> XML view, add the configuration <async_mode>1</async_mode> in the VPN tunnel section, and save the profile.

 

apr-kb2-3.PNG

 

Note: This solution is applicable for both SSL VPN and IPsec VPN tunnels.

 

Once the endpoint machine is synced with the profile, FortiClient will now prompt for Smart Card MFA PIN, and VPN can now be connected.