Rotate Security Certificates

On this page

New in v1.1: CockroachDB allows you to rotate security certificates without restarting nodes.

Tip:

For an introduction to how security certificates work in a secure CockroachDB cluster, see Create Security Certificates.

When to Rotate Certificates

You may need to rotate the node, client, or CA certificates in the following scenarios:

The node, client, or CA certificates are expiring soon.
Your organization's compliance policy requires periodical certificate rotation.
The key (for a node, client, or CA) is compromised.
You need to modify the contents of a certificate, for example, to add another DNS name or the IP address of a load balancer through which a node can be reached. In this case, you would need to rotate only the node certificates.

Rotate Client Certificates

Create a new client certificate and key:

$ cockroach cert create-client <username>
--certs-dir=certs \
--ca-key=my-safe-directory/ca.key

Upload the new client certificate and key to the client using your preferred method.
Have the client use the new client certificate.

This step is application-specific and may require restarting the client.

Rotate Node Certificates

To rotate a node certificate, you create a new node certificate and key and reload them on the node.

Create a new node certificate and key:
```
$ cockroach cert create-node \
<node hostname> \
<node other hostname> \
<node yet another hostname> \
--certs-dir=certs \
--ca-key=my-safe-directory/ca.key \
--overwrite
```
Since you must create the new certificate and key in the same directory as the existing certificate and key, use the --overwrite flag to overwrite the existing files. Also, be sure to specify all addresses at which node can be reached.
Upload the node certificate and key to the node:
```
$ scp certs/node.crt \
certs/node.key \
<username>@<node address>:~/certs
```
Reload the node certificate without restarting the node by issuing a SIGHUP signal to the cockroach process:
```
pkill -SIGHUP -x cockroach
```
The SIGHUP signal must be sent by the same user running the process (e.g., run with sudo if the cockroach process is running under user root).
Verify that certificate rotation was successful using the Local Node Certificates page in the Admin UI: https://<address of node with new certs>:8080/#/reports/certificates/local.

Scroll to the node certificate details and confirm that the Valid Until field shows the new certificate expiration time.

Rotate the CA Certificate

To rotate the CA certificate, you create a new CA key and a combined CA certificate that contains the new CA certificate followed by the old CA certificate, and then you reload the new combined CA certificate on the nodes and clients. Once all nodes and clients have the combined CA certificate, you then create new node and client certificates signed with the new CA certificate and reload those certificates on the nodes and clients as well.

For more background, see Why CockroachDB creates a combined CA certificate and Why rotate CA certificate in advance.

Rename the existing CA key:
```
$ mv  my-safe-directory/ca.key my-safe-directory/ca.old.key
```
Create a new CA certificate and key, using the --overwrite flag to overwrite the old CA certificate:
```
$ cockroach cert create-ca \
--certs-dir=certs \
--ca-key=my-safe-directory/ca.key \
--overwrite
```
This results in the combined CA certificate, ca.crt, which contains the new certificate followed by the old certificate.

Warning:
The CA key is never loaded automatically by cockroach commands, so it should be created in a separate directory, identified by the --ca-key flag.
Upload the new CA certificate to each node:
```
$ scp certs/ca.crt
<username>@<node1 address>:~/certs
```
Upload the new CA certificate to each client using your preferred method.
On each node, reload the CA certificate without restarting the node by issuing a SIGHUP signal to the cockroach process:
```
pkill -SIGHUP -x cockroach
```
The SIGHUP signal must be sent by the same user running the process (e.g., run with sudo if the cockroach process is running under user root).
Reload the CA certificate on each client.

This step is application-specific and may require restarting the client.
Verify that certificate rotation was successful using the Local Node Certificates page in the Admin UI: https://<address of node with new certs>:8080/#/reports/certificates/local.

The details of the old as well as new CA certificates should be shown. Confirm that the Valid Until field of the new CA certificate shows the new certificate expiration time.
Once you are confident that all nodes and clients have the new CA certificate, rotate the node certificates and rotate the client certificates.

Why CockroachDB creates a combined CA certificate

On rotating the CA certificate, the nodes have the new CA certificate after certs directory is rescanned, and the clients have the new CA certificates as and when they are restarted. However, until the node and client certificates are rotated, the nodes and client certificates are still signed with the old CA certificate. Thus the nodes and clients are unable to verify each other's identity using the new CA certificate.

To overcome the issue, we take advantage of the fact that multiple CA certificates can be active at the same time. While verifying the identity of another node or a client, they can check with multiple CA certificates uploaded to them. Thus instead of creating only the new certificate while rotating the CA certificates, CockroachDB creates a combined CA certificate that contains the new CA certificate followed by the old CA certificate. As and when node and client certificates are rotated, the combined CA certificate is used to verify old as well as new node and client certificates.

Why rotate CA certificates in advance

On rotating node and client certificates after rotating the CA certificate, the node and client certificates are signed using new CA certificates. The nodes use the new node and CA certificates as soon as the certs directory on the node is rescanned. However, the clients use the new CA and client certificates only when the clients are restarted. Thus node certificates signed by the new CA certificate are not accepted by clients that do not have the new CA certificate yet. To ensure all nodes and clients have the latest CA certificate, rotate CA certificates on a completely different schedule; ideally, months before changing the node and client certificates.

Pricing

Contact us

Sign In