I have observed that some of the accounting records in the detail-yyyymmdd
file contain “User-Name” value that does not match the ldap user
name that was used in the 802.1x authentication. The details entries correspond
to Mac clients were correct. But the Windows users running SecureW2 were
not. The incorrect accounting records have either “anonymous”
or an user supplied “outer identity” (configurable as EAP type
property via the SecureW2 configuration interface). I am using Cisco
Aironet 1231 and Proxim AP2000. Since the Radius accounting start-stop are
sent by the access point, does it mean that the AP (Radius client) uses the “outer
identity” for Radius accounting records? Could this be a
Radius client configuration error? Though I don’t recall seeing any
configuration options related to Radius client function in the APs. Has anyone
come across with similar situation? Regards Cedric |
- Incorrect User-Name in details accounting records CHui