Skip to content

About remote key generation

With remote key generation, CyberArk Certificate Manager - SaaS has the target machine create a certificate's private key itself. The machine generates the key and keeps it. Nothing copies the key to Certificate Manager - SaaS or anywhere else.

Certificate Manager - SaaS only keeps track of where the key is and installs the certificate next to it.

Benefits

  • Compliance. Some regulations and internal policies require proof that a private key never leaves the machine that uses it. With remote key generation the key exists in exactly one place.
  • Systems that only trust their own keys. Some systems refuse private keys created elsewhere. Remote key generation lets Certificate Manager - SaaS manage their certificates anyway.
  • Less key handling. Certificate Manager - SaaS never transfers, stores, or encrypts a private key for delivery.

Key concepts

Term What it means
Key Generation System The system that creates a certificate's private key. Each machine type that supports remote key generation appears as its own key generation system, for example F5 BIG-IP LTM.
Target The machine that generates the key, and where Certificate Manager - SaaS installs the certificate.
Key Location Where a certificate's private key lives. For remote key generation, this is the machine.
On-device key name Each key gets a new, unique name on the machine. The name is the installation's Certificate Name plus a date and a number, for example www.example.com_26Oct15_0427. Certificate Manager - SaaS removes characters the machine doesn't allow and shortens the name to 63 characters. A new key never overwrites an existing key on the machine.

How a certificate is issued

After you submit a request with a key generated on a machine, the following happens:

  1. Approval. If the request policy requires approval, the request waits for it. The machine doesn't create a key until someone approves the request.
  2. Key creation. The machine creates the private key and reports only its public key.
  3. CSR. The machine creates the certificate signing request (CSR) with that key. Certificate Manager - SaaS checks that the key signed the CSR and that the CSR's common name, subject alternative names, and key match your request.
  4. Issuance. The certificate authority (CA) issues the certificate.
  5. Installation. Certificate Manager - SaaS sets up the installation you chose with the new certificate, next to its key. If you enabled Push certificate on save, Certificate Manager - SaaS pushes the certificate to the machine right away. Otherwise, a provisioning schedule or a manual push installs it later.

If the installation step fails, the certificate stays issued. Fix the cause and provision it again from the machine. You don't need a new certificate.

One certificate, one machine

A certificate whose key was generated on a machine belongs to that machine:

  • It can be installed only on the machine that holds its key. Other machines don't offer it, and Certificate Manager - SaaS refuses to install it anywhere else.
  • Its private key can't be downloaded, exported, or imported into another machine, because Certificate Manager - SaaS never has it.
  • The certificate's Key Location, and the Key Location column of the machine's Installations tab, show where the key is.

To use the same certificate details on another machine, request a new certificate for that machine. That machine generates its own key.

How renewal affects the key

The renewal option you select decides what happens to a key generated on a machine.

Option in the Renew Certificate dialog What happens to the key
Renew with a new private key and CSR. (recommended) The machine creates a new key. Certificate Manager - SaaS copies the certificate details from the original request.
Edit certificate details and renew with a new private key and CSR. The machine creates a new key. The request wizard opens with the machine already selected, so you can change the certificate details.
Renew with the current private key and CSR. The machine keeps the current key. Available only when the request policy has Allow private key reuse selected and the original request is still available.

After a manual renewal, Certificate Manager - SaaS updates the certificate's existing installations to the renewed certificate. A provisioning schedule pushes it to the machine, or you can provision it from the machine yourself.

When you renew with the current private key, the machine replaces the previous certificate stored under the key's name with the renewed one. Everything on the machine that uses that certificate, such as SSL profiles, then serves the renewed certificate.

Note

Renewing with the current key requires the Allow private key reuse option on the request policy, which is off by default. Leave it off if your policy requires a new key at every renewal.

Automatic renewal

Automatic renewal always creates a new key on the same machine. If automatic provisioning is turned on for your organization, Certificate Manager - SaaS pushes the renewed certificate to the machine. Otherwise, provision it from the machine.

If someone removes the machine type's key generation system from the request policy, automatic renewal uses the request policy's first key generation system instead. The new key is then not created on the machine.

Older keys on the machine

On F5 BIG-IP LTM, Certificate Manager - SaaS keeps the current and the previous certificate and key. It deletes older ones, unless an SSL profile still uses them.

Limitations

  • Remote key generation is currently available for F5 BIG-IP LTM. The F5 BIG-IP LTM must be reachable from a VSatellite.
  • Remote key generation doesn't support Federal Information Processing Standards (FIPS) or hardware security module (HSM) key storage on the F5 BIG-IP LTM.
  • Remote key generation supports only the key types and subject fields listed under Supported certificate details.
  • You can't use a CSR that you generate and upload yourself with a key generation system that creates keys on machines.
  • Only Renew with the current private key and CSR. keeps the key. Every other renewal, including automatic renewal, creates a new key.

FAQ

Does this change certificates I already have?

No. Existing certificates and machines work as before. Remote key generation applies only to certificates requested with a key generation system that creates keys on machines.

Who can see the private key?

Nobody through Certificate Manager - SaaS. The key exists only on the machine.