Technical Tip: Captive portal with SAML for wifi users not connecting with error 'Firewall Authentication Failed'
| 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.
This can also be verified with the following SAML debugs:
diagnose debug console timestamp enable Stop the debug processes after collecting the output by using the following commands:
diagnose debug disable diagnose debug reset
As a solution, make sure the group ID is the same on FortiGate and Azure, as shown below:
Alternatively, it can also be edited through the CLI:
Note: Related documents:
|
