Technical Tip: Prerequisites when implementing IPsec VPN SAML-based authentication

[Nivedha]

Description	This article provides prerequisites for configuring IPsec VPN SAML-based authentication.
Scope	FortiGate v7.2+, EMS v7.2+, FortiClient v7.2+, FortiAuthenticator v6.4+.
Solution	Similar to SSL VPN SAML-based authentication, FortiOS 7.2 onwards IPsec VPN also supports SAML-based authentication. The full configuration for the same is listed in IPsec VPN SAML-based authentication and SAML-based authentication for FortiClient remote access dialup IPsec VPN clients Things to consider for this configuration to work: FortiClient should be installed in a non-domain joined device or if domain joined, the device should not be part of the network that FortiGate is on. This is because the device should be on a remote network to connect to IPSec VPN as a remote device. This configuration is only possible with FortiClient as the remote dialup client and not for other devices. When using FortiAuthenticator as the IdP, refer to FortiAuthenticator as an IdP to configure SAML IdP on FortiAuthenticator Use the Test Single Sign-On facility in Azure to check if the Single Sign-On works as expected - Test Single Sign-On  Configure the tunnel with IKEv2 instead of IKEv1. FortiGate does not support SAML-based authentication for IPsec VPN with IKEv1. SAML authentication requires an interactive login process (browser-based authentication flow), which is not supported in IKEv1.  Note: Remote access IPsec VPN user or admin user login authentication to FortiGate using SAML Single Sign-On (SSO) fails after firmware upgrade on FortiGate to v7.6.4. Troubleshooting Tip: SAML Authentication fails after firmware upgrade to 7.6.4