Consider a Win2003 + IIS6 machine that has a single website. Let's call it myDomain.com. The task is to secure the site with an SSL certificate. Currently have a .pfx certificate.
Using the MMC app, the certificate is imported successfully into:
- Current user personal store
- Local Computer personal store
Problem: the myDomain cert doesn't show in the list of available certs when configuring IIS. The only entry is for that 3rd part certificate authority.
We know the cert for myDomain.com is in the .pfx because the MMC import process shows two certs:
- one for myDomain.com with the Intended Purpose of Client Authentication
- one for the Root CA
How can I ensure that the certificate --for myDomain.com-- in the .pfx shows in the pick-list in the IIS Certificate Wizard when choosing "Assign an existing certificate"?
Update It appears that the .pfx created was not suitable for Server Authentication, but rather Client Authentication only.