Troubleshooting Tip: Troubleshooting 'Did not find vendor' errors in RADIUS authentication event logs
| Description | This article provides an overview of how to check the missing Vendor-Specific RADIUS Attributes in FortiAuthenticator. |
| Scope | FortiAuthenticator. |
| Solution | A RADIUS built-in dictionary is the default set of standard RADIUS attributes included with the server. It defines common attribute names, numbers, and data types, allowing RADIUS clients and servers to communicate correctly without adding any custom or vendor-specific dictionaries.
To check the list of supported built-in Radius dictionaries, check the following path: Log in to the FortiAuthenticator GUI -> Authentication -> Radius Service -> Dictionaries -> Built-in Vendors.
Use the browser search function to look for the related Vendor ID. In this test case, 12356 (Fortinet) is used. Select the vendor ID to view supported vendor attributes.
Whenever the vendor-specific attribute is mismatched, the following log can be found (check FortiAuthenticator Radius authentication debug):
2025-12-09T09:03:22.616922+08:00 LAB-FAC radiusd[88888]: (888) eap: Did not find vendor 12356, attr 1 --> "TESTSTRING"
From the log above, vendor '12356' is referring to the FORTINET vendor ID, 'attr 1' referring to 'Attribute Number 1' with name 'Fortinet-Group-Name'. 'TESTSTRING' refers to the 'value/string' of the configured RADIUS attribute.
The Radius attribute of the user needs to be added under the user configuration. The following is a screenshot sample from a local user configuration.
 |
