• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

SSL Certificates (Solved)

T

timbrigham

Junior Member
I?m trying to find information regarding certificate installation for Windows Server 2003 using a professional company, and most everything I?ve found has been for self signed.
I?m using InstantSSL, and I have the actual certificate installed in IIS. I have two other certificates which were sent as well, one which I believe is the certificate from their company. I think this one goes into Certificate Trust List. The third one (labeled ComodoSecurityServicesCA.crt) I believe is the client side certificate so they don?t get prompted for using a non trusted certificate. How do I push this out so they don?t have to install it by hand?
 
You purchased a SSL cert from a company that is not already in the Windows trusted root store? You could've set up your own CA and issued a cert that would accomplish the same thing for free.

Anyway, if you have an AD domain, you can push the root CA cert with a GPO. But if this website needs to be accessed by people that are not in your domain (that you can't manage), there isn't much you can do.
 
The master site for the company is in the master list (GTE CyberTrust Global Root).
The problem looks like there is an inermediate level as well.
I checked that the company was in the master list before starting this.

The certificate window shows the following structure:
GTE CyberTrust Global Root
**Comodo Class 3 Security Services Certificate CA
**** <my certificate>
 
How do I push this out so they don?t have to install it by hand?
Click to expand...

This is done automatically by the web server. Install the intermediate on the server, and it will push it out to clients that need it.

If your certificates are fully PKCS compliant, IIS 6 should be able to install the intermediate automatically, when you install your personal certificate.
 
Problem solved.
For some reason the default location the certificate was installing to wasn?t correct. Specifying the physical certificate store by hand did it.
Thanks guys.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top