Reference: SSL instruction variables
The following variables are used throughout this section to demonstrate how to create local keystore files when configuring SSL on a two node, single datacenter cluster.
Anyone with access to the CA key and signing certificate can authorize hosts as the
Directory where the root certificate is created and stored. DataStax recommends securing this directory, ideally on a computer isolated from the network.
Root CA configuration file.
Title for the section containing the Distinguished Name (DN) properties for the CA.
Password for the generated file used to sign certificates.
Two letter country code, such as <US> for United States or <JP> for Japan. See Nations Online for a complete list of country codes.
Name of your organization.
Name of your DataStax Enterprise (DSE) cluster.
Common Name (CN) for the root CA.
Key file for the root CA certificate.
Certificate used to sign (authorize) DSE node SSL certificates.
Truststore that contains the root certificate.
Use the same truststore that contains the root certificate on all nodes.
Keystore for the individual node.
Password used to protect the individual private key.
Password used to protect the private key of the key pair.
Password required to access the keystore.
Location where the certificate file for each DSE node is created. Typically, SSL certificates and keys are generated on a secure system that is isolated from the network.
Fully Qualified Domain Name (FQDN) of the node, such as
ip-10-200-182-183.example.com. If using the FQDN as the node_name, you can add the IP address as a subject alternative name (SAN) so that the certificate protects the IP address in addition to the domain name.
If using the domain name as the node_name for the CA, add
-extoption. Using the IP address as a subject alternative name (SAN) ensures that the certificate protects the IP address in addition to the domain name. For example:
Certificate signing request (CSR) that is passed to the Certificate Authority (CA) to sign the certificate. The CSR typically includes the public key, plus associated metadata such as the Common Name (CN), Organization (O), Organization Unit (OU), and Country ©.
The signed certificate file to create, using the certificate signing request (CSR) (signing_request.csr) as the input file.
If using the domain name as the node_name and the node IP address as a subject alternative name (SAN), create a temporary configuration file and pass it in using the
-extfileoption. In the configuration file, use the
subjectAltNameparameter to specify the DNS and IP.
You can specify multiple SANs in the same configuration file:
subjectAltName=DNS:domain1,IP:10.200.100.52 subjectAltName=DNS:domain1,IP:10.200.101.63 subjectAltName=DNS:domain1,IP:10.200.111.74 subjectAltName=DNS:domain1,IP:10.200.121.85