Troubleshoot remote key generation¶
Consider the following troubleshooting tips when you generate private keys on your machines with CyberArk Certificate Manager - SaaS.
No key generation system of the request policy can generate a key on this machine¶
You started from a machine, and the request wizard shows None of this template's key generation systems can generate a key on this machine. The request policy doesn't allow that machine type's key generation system.
Select another request policy, or ask a PKI Administrator to add the key generation system to this one.
The machine isn't listed under Target¶
The machine is of a different type than the selected key generation system, hasn't passed its connection test, or doesn't support remote key generation.
Check the machine type, run its connection test, and look for the Remote Key Generation Available chip in its side sheet.
Choose an existing installation is unavailable¶
The wizard shows This machine has no installations to update yet. The machine has no installations.
Use Create a new installation.
The machine's installation settings don't load¶
The wizard shows The machine's installation settings could not be loaded, so an installation cannot be configured here. Please try again later. Certificate Manager - SaaS couldn't retrieve the machine's installation settings.
Try again later. If it persists, check the machine on the Machines page.
The request policy can't be saved¶
The request policy shows This template names ... key generation system(s) that are not available to you. The request policy names key generation systems you don't have access to, so saving would remove them.
Ask an administrator to restore access before you edit the request policy.
Renewing with the current private key is unavailable¶
Renew with the current private key and CSR. is unavailable. The request policy doesn't allow private key reuse, or the original request is no longer available.
Use Renew with a new private key and CSR. (recommended) to renew with a new key, or ask a PKI Administrator to select Allow private key reuse in the request policy.
The request fails after approval¶
Someone approved the request, but the machine couldn't create the key or the certificate signing request (CSR). Common causes:
- The key algorithm, subject, or extensions are outside the supported certificate details.
- The machine was unreachable from the VSatellite, or rejected the operation.
Correct the certificate details or the machine's connection, and then submit the request again. To prevent unsupported key algorithms, limit the request policy's key algorithms to the supported ones.
The certificate's public key doesn't match the machine¶
Certificate Manager - SaaS reports that the certificate's public key doesn't match any key generated on the machine. The certificate's key isn't on this machine, or someone removed the key from the machine.
Install the certificate only on the machine that holds its key. If the key is gone from the machine, request a new certificate.