There are two methods to do that: by the MMC interface, or by the command line. The MMC interface is simpler. You right-click on the brand new certificates, choose “All Duties | Export”, and observe the prompts to export together with the personal key. Nevertheless, the PowerShell instructions are extra versatile, so we’ll element them right here.
We use the next PowerShell instructions in the identical session.
[String]$rootCertPath = Be a part of-Path -Path 'cert:CurrentUserMy' -ChildPath "$($rootCert.Thumbprint)"
This will get the trail to the certificates within the retailer, by means of the $rootCert variable we saved earlier. (That is why you need to difficulty all of those instructions in the identical shell session, so the references to the generated certificates might be re-used.)
Subsequent, we’ll use that certificates to generate two recordsdata, named FakeCA.pfx and FakeCA.crt, in your present working listing. FakeCA.pfx is the personal key related to the certificates, with out which we are able to’t use it, and which have to be password-protected. FakeCA.crt is the certificates itself, written out to a file.
Export-PfxCertificate -Cert $rootCertPath -FilePath 'FakeCA.pfx' -Password ("password" | ConvertTo-SecureString -AsPlainText -Drive)
Export-Certificates -Cert $rootCertPath -FilePath 'FakeCA.crt'
Within the code above, substitute in your individual password the place it says "password". Make sure to retain the quotes.
Step 4: Create a brand new certificates signed by the pretend root authority
This subsequent step generates an precise certificates signed by the pretend root authority we created for this machine. Once more, use the identical PowerShell session for these instructions too.
$testCert = New-SelfSignedCertificate -CertStoreLocation Cert:LocalMachineMy -DnsName "SignedByFakeCA" -KeyExportPolicy Exportable -KeyLength 2048 -KeyUsage DigitalSignature,KeyEncipherment -Signer $rootCert
As with the pretend root authority, this certificates is stored within the machine’s native certificates retailer.
We additionally must export the certificates and its personal key to 2 recordsdata, as we did earlier than. Be certain you utilize the identical password for the personal key that you simply outlined above.
[String]$testCertPath = Be a part of-Path -Path 'cert:LocalMachineMy' -ChildPath "$($testCert.Thumbprint)"
Export-PfxCertificate -Cert $testCertPath -FilePath testcert.pfx -Password ("password" | ConvertTo-SecureString -AsPlainText -Drive)
Export-Certificates -Cert $testCertPath -FilePath testcert.crt
As soon as once more, whenever you’re accomplished, you must have two recordsdata, named testcert.pfx and testcert.crt, in your present working listing.
Step 5: Set up the pretend root authority certificates to the Trusted Root Authorities Retailer
The subsequent step is to make the pretend root authority we created into a completely trusted authority on this machine. After we do that, all certificates signed by that authority might be handled as trusted (once more, solely on this machine). Then we are able to signal any variety of certificates with that authority and have all of them robotically be trusted in the identical surroundings.
Nevertheless, this may solely work on a machine the place the pretend root authority certificates has been set as much as be trusted. That’s by design. Self-signed certificates ought to work solely in environments the place we designate them as reliable.
To belief the pretend root authority, return to the Certificates Supervisor snap-in. Within the right-hand pane, increase “Trusted Root Certification Authorities | Certificates”, then right-click Certificates and choose “All Duties | Import”.
