Sorry to be misleading, turns out the manual WPA2 Enterprise setting uses EAP-LEAP ( I posted before knowing which flavor/s of EAP the supplicant was using). -But which ever EAP flavor the client uses, the controller/AP doesn't care, as long as it's 802.1x. That was my point, that as long as you’re not using one of the flavors that require certificates to be preinstalled, you should be okay using the manual "join". The client will advertise which flavors of EAP it's capable of using and they negotiate which one to use. You’re correct, there are a lot of ways of setting up 802.1x authentication, but it really doesn't matter which flavor of EAP you use, its personal preference related to security/client support/manageability of the certificates. I would never configure LEAP on a client, but apparently that’s what the manual WPA2 Enterprise is using. Here’s a paste from my WCS:
Authenticated Yes
Policy Type WPA2
Encryption Cipher ccmpAes
EAP Type LEAP