Technical Tip: SSL VPN SAML Authentication failure due to missing SAML Metadata on FortiGate
| Description | This article describes an issue where SSL VPN users using SAML authentication are unable to connect when SAML metadata is missing on the FortiGate. The problem occurs when the reserved internal kernel UDP socket 8900 of the SSL VPN process is occupied by the hatalk daemon, causing the sslvpnd process to crash, which in turn leads to the removal of the metadata by FortiGate. |
| Scope | FortiGate v7.2.10. |
| Solution | SSL VPN users using SAML authentication fail to connect in both tunnel mode and web mode. The following errors appear in the SAML debug logs: diagnose debug application samld -1 It is observed that the saml metadata file gets deleted and the UDP kernel socket 8900 is bound to the hatalk daemon instead of sslvpnd process. This process is responsible for creating the SAML metadata when all sslvpnd processes are restarted. As a result, the SAML metadata cannot be generated, which can be verified using the following commands: diagnose vpn ssl saml-metadata <SAML name> This issue has been resolved in FortiOS versions 7.4.8 and 7.6.3.
Workaround 1:
SAML metadata is also not generated when the configuration has an incorrect/invalid idp-cert. Workaround2:
General debug information required by FortiGate TAC for investigation:
diagnose debug application samld -1
Reproduce the issue,
diagnose debug disable diagnose debug reset diagnose vpn ssl saml-metadata <SAML name>
execute tac report
|
