Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
You may experience some slow load times, errors, and slight inconsistencies. We ask for your patience as we finalize the launch. Thank you.

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

EAP-TLS machine authentication ACS 5.2

Hi, we have a customer with a wifi deployment aruba 3600 controller based. Corporate SSID authentication is EAP-TLS double machine and user authentication through ACS 4.2 against AD and Microsoft AC PKI infraestructure based; it was working ok. After migrating from ACS 4.2 to 5.2, both authenticacion (machine and user) are reported as succeed by ACS but aruba controller does not recognize machine authentication. It seems that controller sees two authentication users and not an machine followed by and user one. We have revised configuration in detail and it seems correct. We begin thinking it could be a bug . We would apreciate any help. Thanks in advance

  • AAA Identity and NAC

EAP-TLS machine authentication ACS 5.2

Can you elaborate your issue further on the aruba end, is the client not able to access the network or is the most recent username in the aruba client tables showing up as the user account?


tarik Admani

Tarik Admani *Please rate helpful posts*
New Member

EAP-TLS machine authentication ACS 5.2

When eap-tls machine authentication works fine aruba controller keeps the client MAC address in the local-userdb as cached evidence that a good machine authentication has occurred. This client MAC address is kept for a certain amount of time, which is based on the "caching period". It works in this way with acs 4.2 but we never see client MAC with ACS 5.2. However, ACS reports a successful authenication with machine FQDN (it reports RADIS name=host/ and ACS