ClientSSL Profile. Key and Cert mismatch. Applying to Virtual Server

Your plan is correct - you only need a clientssl profile. The certificate and key must "match" but they won't match - They aren't identical files, so md5sum won't help you, but the CSR must be generated based on the key that was created. If you created the CSR on the F5, it will automatically create the associated key. Once you obtain the certificate from your certificate authority using the CSR that was generated, you then upload the certificate, matching it to the key you created (System | File Management | SSL Certificate List | click on the key you created, import the certificate).

Hey Shaggy,

I found out the issue. It appeared to be related to the DNS name. I had generated the CSR with the short name since it was an internal site. However, I found utilizing the FQDN resolved the issue. Do you have any explanation why?

Is it because DNS is tied to the FQDN?

Could I create an irule to add on the domain for users who use short name?

Could I create an irule to add on the domain for users who use short name?

certificate uses short name, doesn't it? we can configure http redirect to fqdn but user will get certificate warning message (because fqdn does not match short name in the certificate).

Could I create an irule to add on the domain for users who use short name?

certificate uses short name, doesn't it? we can configure http redirect to fqdn but user will get certificate warning message (because fqdn does not match short name in the certificate).

I usually gen the certificate with the FQDN as the common name, and then the short name as a SAN on the certificate. Make sure you specify the FQDN as a SAN as well(so 2 SAN's, short and FQDN) as I have had problems in the past with browsers ignoring the CN when a SAN is present.