Third Party Certificate Not Verified when connecting via EAP-PEAP
Posted on 2013-12-22
We have a AAA server based on Windows Server 2008, and got everything configured correctly, and went ahead and purchased an SSL Certificate from Godaddy so that our wireless customers wouldn't get any issues connecting.
Wireless Security is EAP-PEAP (WPA2-Enterprise), and the Controller is Cisco WLC.
The issue is after successfully installing the certificate to the server, the clients are getting this error message:
The server "XXXXX" presented a valid certificate issued by "Go Daddy Class 2 Certification Authority", but "Go Daddy Class 2 Certification Authority" is not configured as a valid trust anchor for this profile. Further, the server "XXXXX" is not configured as a valid NPS server to connect to for this profile.
The certificate works fine when connecting via HTTPS or Remote Desktop, but when connecting via wireless, it throws the above error, yet giving the clients the option to "Connect" or "Terminate", but that freaks some of them out.
Bear in mind that all devices (iPhones, iPads, Android Windows 7) have the "Not Verified" warning that pops, but each with its own details, so it's not only a Win7 issue.
Note that we've purchased a third party certificate to avoid getting any warning, but that's what we ended up with.
How can I solve this issue?