pfx file that you will use to sign your deployments. (( relevant quotes from the article are below )) If your CSR was generated for, you MUST provide the same at this step. If you asked for a wildcard, your CA must have approved and generated a wildcard and you must use the same. Now provide a proper "friendly name" ( *.yourdomain.example, yourdomain.example,, etc.) THIS IS IMPORTANT! This MUST match what you setup the CSR for and what your CA provided you. Then you take the CER/CRT file they give you, go back to IIS, "Complete Certificate Request" in the same place you generated the request.
You then give that CSR to your CA and ask for a certificate. This will give you a CSR prepped for IIS.
Use IIS "Server Certificates" UI to "Generate Certificate Request" (the details of this request are out of the scope of this article but those details are critical). SSL Certs for IIS with PFX once and for all - SSL and IIS Explained. I can almost guarantee that the problem is that you expect to be able to use the key and cer files provided by your CA but they aren't based on "the IIS way". You also don't need the personal key given to you by your CA. You do NOT need openssl or makecert or any of that.
0 kommentar(er)
