Created on
08-26-2025
07:28 AM
Edited on
09-02-2025
01:38 AM
By
Jean-Philippe_P
Description |
This article describes which settings should be checked on the FortiClient side when facing a gateway validation failed error in FortiGate debug in IPsec VPN with SAML-based authentication setup. |
Scope | FortiGate, FortiClient. |
Solution |
This article describes a possible issue that can occur when using SAML authentication with IPsec. When EAP is enabled, the gateway validation failed error can still occur, and after some time, the connection expires due to phase1 down.
Settings to check:
Example, if the parameter is enabled:
xAuth enabled on FortiClient:
Debug from FortiGate:
ike 1:SRA_SAML:165: received FCT-UID = 9B05711EA27E4E66B7C6BD5721D1DD06
Example, if the parameter is disabled:
xAuth disabled on FortiClient:
Debug from FortiGate:
ike 1:SRA_SAML:167: received FCT-UID = 9B05711EA27E4E66B7C6BD5721D1DD06
If the xAuth is disabled in FortiClient, the gateway validation will fail.
Useful commands to check the debugs in FortiGate:
diagnose debug reset diagnose debug console time enable diagnose debug application fnbamd -1 diagnose debug application samld -1 diagnose debug application eap_proxy -1 diagnose vpn ike log filter rem-addr4 <RemoteClientIp> diagnose debug application ike -1 diagnose debug enable |
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.