The browser is indicating that it does not trust the certificate. The explanation makes me think you are using the self-signed certificate that came with the controller for web auth. If so, then you need to either configure all of your machines to trust that certificate, or install a 3rd Party certificate on the controller that your machines already trust.
Here's some good 3rd Party certificate info:
Since you will need to purchase a certificate, make sure you get a root CA cert if you are running any code lower than 5.1.151 or else you can go with a chained cert. In my opinion, RapidSSL is cheap and they give you a root ca certificate which of course can be used in and version of code.
Also, you probably want to have a dns name instead of 126.96.36.199 for your cert. To do this, we created another zone so we could resolve 188.8.131.52 to "wireless-auth.uoregon.edu". It's a bit hokey, but the dns name is more meaningful to users than the ip address.
How did you get a chained cert to work? I've tried and never been successful. We're running 5.2 and 6.0 code. Right now we're using a root-signed Thawte cert for wireless auth.
I have never tried to use a chained cert, since using a root ca cert seems easier. There have been a couple post on chained cert, but I have not seen any instructions on how to combine the certs to be able to upload.
I think I have it working with 184.108.40.206 code for webauth. I'll know more soon.
Does anyone know if this soltion also apply to Cisco 5508 Series Wireless Controller?.
See attached pictures
I got the same issue.
Microsoft MCSA/MCSE : 2000 + Security
Guest configuration is the same for all WLC's even the 5500's. What code are you running on the 5508? I know there is an issue with 3rd party certs on the 220.127.116.11 and upgrading to 18.104.22.168 fixes the problem. It seems that with the 6.0.182, the certificate doesn't load properly.