Generate Self-signed Certificates
This document provides an example of using openssl
to generate a self-signed certificate. You can also generate certificates and keys that meet requirements according to your demands.
Assume that the topology of the instance cluster is as follows:
Name | Host IP | Services |
---|---|---|
node1 | 172.16.10.11 | DM-master1 |
node2 | 172.16.10.12 | DM-master2 |
node3 | 172.16.10.13 | DM-master3 |
node4 | 172.16.10.14 | DM-worker1 |
node5 | 172.16.10.15 | DM-worker2 |
node6 | 172.16.10.16 | DM-worker3 |
Install OpenSSL
For Debian or Ubuntu OS:
apt install opensslFor RedHat or CentOS OS:
yum install openssl
You can also refer to OpenSSL's official download document for installation.
Generate the CA certificate
A certificate authority (CA) is a trusted entity that issues digital certificates. In practice, contact your administrator to issue the certificate or use a trusted CA. CA manages multiple certificate pairs. Here you only need to generate an original pair of certificates as follows.
Generate the CA key:
openssl genrsa -out ca-key.pem 4096Generate the CA certificates:
openssl req -new -x509 -days 1000 -key ca-key.pem -out ca.pemValidate the CA certificates:
openssl x509 -text -in ca.pem -noout
Issue certificates for individual components
Certificates that might be used in the cluster
- The
master
certificate used by DM-master to authenticate DM-master for other components. - The
worker
certificate used by DM-worker to authenticate DM-worker for other components. - The
client
certificate used by dmctl to authenticate clients for DM-master and DM-worker.
Issue certificates for DM-master
To issue a certificate to a DM-master instance, perform the following steps:
Generate the private key corresponding to the certificate:
openssl genrsa -out master-key.pem 2048Make a copy of the OpenSSL configuration template file (Refer to the actual location of your template file because it might have more than one location):
cp /usr/lib/ssl/openssl.cnf .If you do not know the actual location, look for it in the root directory:
find / -name openssl.cnfEdit
openssl.cnf
, addreq_extensions = v3_req
under the[ req ]
field, and addsubjectAltName = @alt_names
under the[ v3_req ]
field. Finally, create a new field and edit the information ofSubject Alternative Name
(SAN) according to the cluster topology description above.[ alt_names ] IP.1 = 127.0.0.1 IP.2 = 172.16.10.11 IP.3 = 172.16.10.12 IP.4 = 172.16.10.13The following checking items of SAN are currently supported:
IP
DNS
URI
Save the
openssl.cnf
file, and generate the certificate request file: (When giving input toCommon Name (e.g. server FQDN or YOUR name) []:
, you assign a Common Name (CN) to the certificate, such asdm
. It is used by the server to validate the identity of the client. Each component does not enable the validation by default. You can enable it in the configuration file.)openssl req -new -key master-key.pem -out master-cert.pem -config openssl.cnfIssue and generate the certificate:
openssl x509 -req -days 365 -CA ca.pem -CAkey ca-key.pem -CAcreateserial -in master-cert.pem -out master-cert.pem -extensions v3_req -extfile openssl.cnfVerify that the certificate includes the SAN field (optional):
openssl x509 -text -in master-cert.pem -nooutConfirm that the following files exist in your current directory:
ca.pem master-cert.pem master-key.pem
Issue certificates for the client (dmctl)
To issue a certificate to the client (dmctl), perform the following steps:
Generate the private key corresponding to the certificate:
openssl genrsa -out client-key.pem 2048Generate the certificate request file (in this step, you can also assign a Common Name to the certificate, which is used to allow the server to validate the identity of the client. Each component does not enable the validation by default, and you can enable it in the configuration file):
openssl req -new -key client-key.pem -out client-cert.pemIssue and generate the certificate:
openssl x509 -req -days 365 -CA ca.pem -CAkey ca-key.pem -CAcreateserial -in client-cert.pem -out client-cert.pem