Generating self-signed certificates on Windows
<p>If you do anything with Identity, you’ll know you need certificates — lots of them — and that normally means self-signed to keep the costs down or because you just need it for a short time before you tear down the VM or because you don’t have a PKI infrastructure.</p>
<p>This is for testing, proofs of concept etc. This is definitely <strong>not</strong> for Production purposes. Use at <strong>your own risk</strong>.</p>
<p>This self-signed certificate also needs a private key otherwise it’s pretty useless for SSL, token signing etc.</p>
<p>Remember that this won’t be signed by a CA so you need to do <a href="https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/how-to-create-temporary-certificates-for-use-during-development#installing-a-certificate-in-the-trusted-root-certification-authorities-store" rel="noopener ugc nofollow" target="_blank">this </a>to stop the browser complaining once you’ve generated the certificates.</p>
<p><strong>Note:</strong> The “ character displayed by Medium does something funny when you cut and paste and run the command. You need to retype it as a “straight” character.</p>
<p><a href="https://medium.com/the-new-control-plane/generating-self-signed-certificates-on-windows-7812a600c2d8"><strong>Click Here</strong></a></p>