• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5004
  • Last Modified:

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?
0
slinky9111
Asked:
slinky9111
  • 5
  • 4
1 Solution
 
askincakirCommented:
Hi,
Did you configure NPS to use the new certificate for PEAP in profile ?

Br,
0
 
slinky9111Author Commented:
Hi,

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.
0
 
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.
0
 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

 
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.
0
 
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...

https://supportforums.cisco.com/thread/2203638
0
 
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.
0
 
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.

http://blogs.citrix.com/2010/01/20/how-to-fix-godaddy-server-certificate-trust-issue-on-safari-and-iphone/

http://hunterford.me/godaddy-ssl-certificate-and-chrome/

http://www.chicagotech.net/wireless/wifi-enterprise1.htm
(This is for a different issuing CA, but the same problem)
0
 
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.
0
 
Craig BeckCommented:
There are plenty...

Digicert, Verisign, Thawte, Comodo, to name a few.
0
 
slinky9111Author Commented:
Thanks for the answers, appreciate the effort
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now