Third Party Certificate Not Verified when connecting via EAP-PEAP

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?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Did you configure NPS to use the new certificate for PEAP in profile ?

slinky9111Author Commented:

Ofcourse, or else how did the clients successfully connected after clicking connect.

And how did the certificate end up being read by the client when connected.

It's because it's been selected from NPS, and by the way, the AAA server is not MS NPS, but is Aradial, but again, the certificate is selected to be used with our clients.
Craig BeckCommented:
I know there used to be issues with GoDaddy certificates if the complete certificate chain wasn't present on the client device.  IIRC the Intermediate CA certificate was missing.  This may be what you're experiencing.
Introduction to Web Design

Develop a strong foundation and understanding of web design by learning HTML, CSS, and additional tools to help you develop your own website.

slinky9111Author Commented:
Ok, I've downloaded the Intermediate Certificate from Godaddy, and imported it into the server.

So are you telling me that the Intermediate Certificate is missing form the Server or from the Client?

If it's missing from the Server, then I must be placing it in the wrong location.

But if you're saying that it's missing from the Client machine, then I'm guessing that every Certificate is going to miss the intermediate certificate, because only the CA is present in the Client machine and not the Intermediate.

I'm no expert in Certificates, and this is my first purchased certificate to be used in AAA, so is there another provider that provides something different?

Correct me if I'm wrong, because I'm a bit confused here.
Craig BeckCommented:
The intermediate certificate needs to be trusted by the client, therefore every client needs the Intermediate certificate.

This kind of explains the issue...
slinky9111Author Commented:
It says in the link you provided that it needs to trust the CA not the intermediate.

It also says that it's an issue with windows machines, but it's not, all devices has the same behaviour.

But what makes me think there's still a solution, (because you're almost saying there isn't), is that the clients connect to the same server, using the same certificate without any warnings, using other protocols, like when using HTTPS or Remote Desktop, yet has an issue with PEAP.
Craig BeckCommented:
Yes there is a solution - install the intermediate certificate on the client.

The client will only trust the CA certificate if it also trusts the intermediate certificate.  As I said, this is a known issue with GoDaddy certificates.  The client needs to trust a chain of certificates or the chain is broken and identity verification will not work.
(This is for a different issuing CA, but the same problem)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
slinky9111Author Commented:
Ok, so the issue is with Godaddy certificate generated from an intermediate certificate.

So, is there any provider that issues certificates from a CA directly?

That's because it's impossible to download the certificate to the client devices in our case.
Craig BeckCommented:
There are plenty...

Digicert, Verisign, Thawte, Comodo, to name a few.
slinky9111Author Commented:
Thanks for the answers, appreciate the effort
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.