AFP548 Changing the world one server at a time.

802.1x, signed Certs, and Trusts

Home › Forums › OS X Server and Client Discussion › Misc. › 802.1x, signed Certs, and Trusts

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #377284
    alexe
    Participant

    I’m setting up 802.1x authentication on our wireless network. We have a RADIUS server with a signed public certificate from Verisign that appears to the clients as valid. However, the clients get a notification: “The Server certificate is not trusted because there are no explicit trust settings.”
    I cannot figure out how to get this certificate to be trusted by default by the clients. Ideally this would be transparent, and the user would only see a cert warning for an invalid certificate.

    Is this behavior by design?

    #377291
    alexe
    Participant

    Because while they are notified that there is “no explicit trust setting” for the Server Certificate, if they choose to inspect the certificate, they can see a green check indicating that the cert is valid; they can also see that it is issued by VeriSign and a list of related Certificates: “Class 3 Public Primary Certification Authority -G2 ->VeriSign Class 3 WLAN Secure Server CA -> (FQDN of our RADIUS server)”.
    When they inspect the certificate, they are given the option to “Always Trust” (FQDN of our RADIUS server) but ideally, since it’s a valid cert, there would be no user interaction…

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.