Ssl – Installing Private and Public Key Certificates On IIS7

iisiis-7sslssl-certificate

I'm not an expert on IIS but every year I really struggle getting a certificate onto an IIS7 server that hosts our ecommerce website.

I buy my certificates via 123-reg and I get a GlobalSign private key and a public key sent to me for the certificate.

The 123-reg help pages are useless and it never works following their instructions, because the instructions dont explain how to use the private key during installation.

There must be an easier way to get this stuff installed as it seems such an ordinary thing to do, and I cannot work out what I'm missing. I dread this coming around every year, and I usually end up installing a load of freebie apps until one generates a file that IIS understands.

Can anyone tell me if there is a simple way to take a private and a public key text file and end up with a certificate ready to be used on my IIS7 website.

Many thanks in anticipation.

Best Answer

Personally, I tend to use OpenSSL for this type of work: http://www.openssl.org/

If you're not dealing with certificates everyday, however, try something along the lines of: http://www.edwinbush.com/my-tools-page/pfx-generator which will combine your Private Key and the Certificate hashes into a PFX file that you can import to your certificate keystore as follows:

  1. Click Start
  2. Click Run...
  3. Type "mmc" and hit Enter
  4. File => Add/Remove Snap-in...
  5. Add Certificates 5a. Select "Computer Account" and hit Next 5b. Select "Local Computer" and hit Finish 5c. Hit OK
  6. Expand the Certificates node in the tree and select Personal
  7. Right click in the central pane
  8. All tasks => Import => Next 8a. Browse to where you saved the PFX file and hit Next --You may need to change the 'Filetype' field to 'All Files' 8b. Check the 'Mark as Exportable' box 8c. Keep all extended properties 8d. Place this certificate into the right store automatically 8e. Hit Finish

This certificate should be available for selection within IIS now when you go to set an HTTPS binding.

Oh, and one more thing - your CA may have provided you with intermediary/root chaining certificates when the certificate was issued. Ensure you install these into the relevant stores too, otherwise you'll have issues with IE. Firefox tends to be alright.

~MBT

Related Topic