Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Because your post suggests that want to do this to avoid purchasing an SSL certificate before your testing is complete, I wanted to ask: To save yourself some time, could you just create your own self-signed certificate using <code>makecert</code>?</p> <p>If so, these notes might be of some help.</p> <p>To create root certificate key files...</p> <pre><code>makecert -r -pe -n "CN=My Own Authority,O=My Company,C=US" -ss CA -sr CurrentUser -a sha1 -sky signature -sv mycert.pvk mycert.cer </code></pre> <p>To create a .PFX file...</p> <pre><code>makecert -pe -n "CN=localhost" -a sha1 -sky exchange -eku 1.3.6.1.5.5.7.3.1 -ic mycert.cer -iv mycert.pvk -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12 -sv localhost.pvk localhost.cer pvk2pfx -pvk localhost.pvk -spc localhost.cer -pfx localhost.pfx </code></pre> <p>Then, using the Certificates snap-in, import the <code>mycert.cer</code> file into the Trusted Root Certification Authorities on the local computer to tell those apps running on the local machine that any certificate signed by your own authority is trustworty.</p> <p>Next, you import the <code>localhost.pfx</code> file into the Personal store on the local computer. (Doing this makes the certificate available to IIS so that it may declare itself, by your own authority, to be the server named "localhost".)</p> <p>There's a detailed descripton of how to import the .PFX file into IIS 7 here: <a href="http://www.digicert.com/ssl-support/pfx-import-export-iis-7.htm" rel="nofollow">http://www.digicert.com/ssl-support/pfx-import-export-iis-7.htm</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload