If the problem is not cured and the private key remains non-exportable, continue. Starting a command prompt and enter the following command, as it mightĬure your problem: certutil -repairstore my 693867F321B5764E324F3FB8C5CBCE03CDA3C2A3 In this sample the thumb is 693867F321B5764E324F3FB8C5CBCE03CDA3C2A3.Īt this point, depending on the root cause of your problem, we suggest We located the Thumbprint of the certificate with the non-exportable private key: NOTE: THE PLACE THAT YOU IMPORT CERTIFICATES IS IMPORTANT! Using mmc we imported both certificates in Local Computer\Personal. If it fails, then your only option would be to create a CSR with exportable private key and re-issue your certificate and re-configure your domains. If it succeeds then your will get your private key exported. There are guides on the internet that the following process might work without the old certificate but in our case it did not, possibly because the certificate was re-issued.ĭISCLAIMER: the following process is not intrusive on your computer and requires a VM to work with. Luckily we had a previous certificate available with exportable private key to work with. The certificate had recently been re-issued using the old CSR but somehow the new certificate’s private key was marked as non-exportable, while past certificates had exportable private keys. We realized that the certificate had lost its ability to export the private key. We needed to export the private key of our IIS7 SSL certificate in order to import it in a node.js HTTPS project operating on a different port under the same domain. Recovering a certificate where the private key is marked as non-exportable
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |