Description | This article describes the steps to use to troubleshoot why a client may not be provisioned the correct network access for Fortinet SSO integrations with the FortiGate. |
Scope | Version: 8.x, 9.x |
Solution |
1) Verify the correct Network Access policy matches. Right click on the host in the host view and select Policy Details. If policy does not match under the Network Access tab or is blank, see KB article 197123.
2) If the correct policy matches, verify correct tag/group sent to the FortiGate using SSO.
Enable debugs (written to /bsc/campusMgr/master_loader/output.master):
Example tf output.master | grep -i "00:21:70:D1:92:77"
3) Have client connect.
4) Review output.master for messages below.
Example 1:
yams.fortinet.fsso FINE :: 2019-04-03 08:30:44:395 :: Sending logon information
Example 2:
yams.SSOManager FINER :: 2021-11-11 15:50:08:801 :: SSOManager.remMessageFromQueue message removed UserIDMessage[logon, mac=24:77:03:07:E6:18, ip=172.16.196.10, user=test, tags=[VPN-Authorized]] for key 24:77:03:07:E6:18
5) Review address ranges defined for VPN management.
FortiNAC versions 9.2 and above
FortiNAC versions 9.1 and below
Expected output:
Example:
If the VPNManagedNetworks value is not present in the device model, read the VLANs on the FortiGate.
From the CLI type:
6) Once troubleshooting is complete, disable debugging:
|