The next steps reconfigure the CA while maintaining the existing certificate. In this case it is necessary to link the existing certificate with the new CNG key storage provider. Before reconfiguring the CA it is recommended to delete the existing private key in the old storage provider. To do so, carry out the following steps.
-
Open a PowerShell with administrator rights.
-
Get the details of your CA certificates, by using the Microsoft command line tool
certutil –store my <Your CA common name>and make a note of the value for Cert Hash.
|
›_ PowerShell |
|---|
|
-
Delete the existing CA certificate and private key.
-
Change the path to the local certificate store.
-
|
›_ PowerShell |
|---|
|
b. Using the value for Cert Hash that you noted down in step 2, run the following command to delete the certificate and private key from the local machine.
|
›_ PowerShell |
|---|
|
c. Repeat the previous step for all CA certificates that were identified when you ran the certutil command.
-
Migrate the CA certificate to the Utimaco CNG provider by running the following command:
|
›_ PowerShell |
|---|
|
-
Link the existing CA certificate with the private key in the new key storage by using the Microsoft command line tool
certutil –f -repairstore -csp "Utimaco Cryptoserver Key Storage Provider" my <Cert Hash>.
|
›_ PowerShell |
|---|
|
-
Import registry settings for the CSP.
-
Create a registry file named
Csp.regthat has the following values, and replace<Your CA Common Name>with your CA common name:
-
|
Csp.cfg |
|---|
|
b. Before you save the file, confirm that you are using SHA1 by running one of the following commands:
i. In case the old CA used a CSP provider:
|
›_ PowerShell |
|---|
|
If you do not see SHA1 in your output, modify the CNGHashAlgorithm key value in the file to have the appropriate name.
ii. In case the old CA used a CNG provider:
|
›_ PowerShell |
|---|
|
If you do not see SHA1 in your output, modify the CNGHashAlgorithm key value in the file to have the appropriate name.
c. Save the file and then run it.
|
›_ PowerShell |
|---|
|
-
Import registry settings for the CSP encryption settings.
-
Create a registry file named
EncryptionCsp.regthat has the following values, and replace<Your CA Common Name>with your CA common name:
-
|
|
|---|
|
b. Before you save the file, confirm that you are using 3DES by running one of the following commands:
i. In case the old CA used a CSP provider:
|
›_ PowerShell |
|---|
|
If you do not see 3DES in your output, modify the CNGEncryptionAlgorithm key value in the file to have the appropriate name.
ii. In case the old CA used a CNG provider:
|
›_ PowerShell |
|---|
|
If you do not see 3DES in your output, modify the CNGEncryptionAlgorithm key value in the file to have the appropriate name.
c. Save the file and then run it.
|
›_ PowerShell |
|---|
|
-
Optional but strongly recommended: Change the CA hash algorithm to SHA-2 family, for example SHA256.
|
›_ PowerShell |
|---|
|
-
Start the CA service again.
|
›_ PowerShell |
|---|
|