RE: Wildcard certificate

Rob,

We went through this same process several years ago.
Now we have one wildcard cert, *.pencor.com.
I didn't do the work, our IT staff took care of this.

I do remember that I struggled to import the new wildcard cert into DCM.
The old wildcart SHA1 cert had 1 root CA, 1 intermediate CA, 1 private key.
The new wildcard SHA256 cert had 1 root CA, 2 intermediate CAs, 1 private key.

DCM did not have the newer updated SHA256 CA from GEOTRUST, which was causing the import issue.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Wednesday, April 06, 2016 10:59 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Wildcard certificate

We are switching over some of our sites from names like dekkocustomers.com, dekkosuppliers.com and so on to names like customers.dekko.com suppliers.dekko.com.
One goal is to be able to use one certificate for all.

When I view the certificate via FF I see:

Website: customers.dekko.com
Issued To
Common Name (CN) *.dekko.com
Organization (O) Group Dekko, Inc
Organizational Unit (OU) <Not Part Of Certificate>

Our external scanning service does an nslookup on the IP address associated with that website and it returns customers.dekko.com (as it should). It then compares that to the certificate and says that customers.dekko.com doesn't match *.dekko.com.

One could argue that the scanning service needs to figure this out. I haven't got a year to spare on this.

If I just get another certificate and just leave the CN dekko.com instead of *.dekko.com will this work (as a general rule)?


Rob Berendt