Technical Tip : Captive portal with SAML for wifi users not connecting with error 'Firewall Authentication Failed'

[vermap]

Description	This article describes the troubleshooting steps when the captive portal with SAML authentication with the WiFi users failed to load with the error 'Firewall Authentication Failed'.
Scope	FortiGate.
Solution	When connecting to the WiFi SSID and trying to access the captive portal page with SAML authentication, the page gets redirected but gives the error 'Firewall Authentication Failed': This happens because of the mismatch between the User group ID in FortiGate and Azure. Make sure the group ID is the same on FortiGate and Azure as shown below Alternatively, it can also be edited through CLI Related documents: Captive portal authentication using SAML credentials  Technical Tip: Configure SAML SSO for WiFi SSID over Captive Portal with Azure AD as IdP