Do I need a certificate on a WLC when using webauth on an anchor controller
I'm configuring a new WLAN controller to talk to an existing anchor controller. I didn't think I need a certificate on a WLC on the foreign controller, only on the anchor controller, which is up and working and has many controllers linked to if for guest traffic.
This new controller is up, the mobility tunnel is up, but when I associate to the guest WLAN, I get the "There is a problem with this website's security certificate"
I didn't think that is how it worked. I didn't think I had to put a cert on this controller. Unless there is some other configuration I am missing.
The WLC by default uses a self-signed certificate which all clients will not trust. This means that each and every client will have to accept the certificate warning on the browser prior to being allowed access to the login screen.
The only way to negate this to use open ssl to generate a Certificate Signing Request (CSR) & a CA such as Verisign/GoDaddy which most clients will have in their trust list by default.