Forum Discussion
Client x509 Incorrect Certificate Chain
Hello,
For our HTTPS services we require a certificate from the user. In some cases we are seeing that the user's browser is building an incorrect certificate chain which then results in a SSL::verify result code of 27. What have been doing so far to remedy this issue is to work with the users by first exporting, deleting, and then finally reimporting the certs that are causing the issue as 'Untrusted'.
Good certificate chain
----------------------
Correct Root CA 1
===> Correct Intermediate CA
=======> Correct Client Cert
Bad certificate chain
----------------------
Incorrect Root CA
===> Incorrect CA
======> Correct Root CA 1
=========> Correct Intermediate CA
============> Correct Client CertIs there a better way to do this? I don't currently have the Chain setting configured in the Client SSL profile though in some limited testing it didn't seem to fix the issue. We do have the Advertised Certificate Authorities set and the bundle doesn't include the offending certificates.
Thanks
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com