Technical Tip: How to configure FortiNAC to send the 'Message-Authenticator' attribute in Access-Accept message through RADIUS Authentication
| Description | This article describes how to fix the 'Authentication Failure' issue due to the missing 'Message-Authenticator' attribute that is mandatory with FortiOS v7.2.10 or v7.4.5. |
| Scope | FortiNAC, FortiNAC-F. |
| Solution | In case of a RADIUS Authentication with EAP, FortiNAC will send 'Access-Accept', 'Access-Reject', or 'Access-Challenge' messages with the 'Message-Authenticator' attribute. However, when MAB is in use, the 'Message-Authenticator' attribute will not be sent by FortiNAC by default, and authentication will fail with FortiOS v7.2.10 or v7.4.5.
[1156] __rad_chk_resp_authenticator-No Message Authenticator By following the steps below, the 'Message-Authenticator' can be enabled for MAB.
Note: Since the FortiGate test Radius request with username test01 will not match any 'Network Access Policy' and 'Logical Network', and FortiGate does not use EAP for test 'Radius-Request', FortiNAC will send an 'Access-Accept' without any additional RADIUS Attributes. As a consequence, FortiGate will still state an 'Invalid secret for the server'.
2nd option: |






