Showing results for 
Search instead for 
Did you mean: 

CAPWAP AP 802.1x supplicant with EAP-TLS


Hello Community!


We have a highly secure environment with NAC on switchports. We need APs to use pre-provisioned(during staging) LSC certificates (same for DTLS encryption and AP Auth on the WLC) during 802.1x EAP-TLS authentication on the NAC switchports. We had already chained WLC with root CA and provisioned LSC certs to all APs as "802.1x + CAPWAP-DTLS". APs are using LSC certs for both CAPWAP Data and Control DTLS encryption. NAC is not enabled on the switch ports to which APs are connected yet.


The issue is when we try enable "802.1x Authentication" in "802.1x Supplicant Credentials" as EAP-TLS in Access Points Global configuration in GUI, the WLC asking for username and password. (The picture is from the configuration guide).


That's confusing, since we intend to use EAP-TLS which require certificate instead of credentials. Configuration guides referred to this feature says: "Also configure user name and password."

What will those username/password be?



7 Replies 7

Haydn Andrews

Depending on what WLC version you are running the only 802.1x auth for the AP to the network is EAP-FAST.



Prior to rel 8.7, AP port 802.1x only supported EAP-FAST, in rel 8.7 the AP supplicant will also support EAP-TLS / EAP-PEAP

*****Help out other by using the rating system and marking answered questions as "Answered"*****
*** Please rate helpful posts ***

Thanks for you reply!


It's 8.10.105, so this feature is supported, and we have an option to choose EAP-TLS as authentication method. We just still being asked for a username and password when we choose it. 




Any ideas?

When I try to enable 802.1x Authentication:




I get this error:



What's Global 802.1x Username? I want to use EAP-TLS...


Hello Murinos,


Did you figure out how to solve this ? If you configure EAP-TLS without any username/password set, is it working ?



Hello aleopoldie,


No, we bumped to another problem. The ISE we use as AAA server for NAC can't trust the Root CA we use for SCEP on WLC. So, it will not accept certificates we issue for APs for EAP-TLS.

We are bound with EAP-FAST (login/pass) and mac check. 


Bump ? - Any news on this , we are all holding our collective breaths in anticipation



Unfortunately, no. 

We were not allowed to power on 'main' root CA which is used for all production networking infrastructure. The 'additional' root CA which is used for SCEP on WLC and APs cant' be made trusted on ISE. ISE can trust only single root CA (2 years ago). So it could not auntheticate AP's certificates issued by 'additional' root CA on NAC port.

The task is done and we left the site, so it's final.

If only ISE could support several root CA's that time, then it could be possible to meke everything right. 

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers