How To Use Custom Certs In The Management Plane

Problem

As part of security enhancements, we would need to use the custom certs in the Platform9 Management Plane.

Environment

  • Platform9 Edge Cloud - LTS-2 and Higher.

Procedure

Steps to use your own CA and certs that Platform9 have used.

Note that depending on the CA you are using some steps may vary:

a. Create a csr.conf file with values based on our env:

[req]
default_bits = 4096
distinguished_name = req_distinguished_name
req_extensions = req_ext
prompt = no

[req_distinguished_name]
C = US
ST = CA
L = Mountain View
OU = Testing
CN = airctl-1-2662399-213.pf9.localnet # DU FQDN

[req_ext]
subjectAltName = @alt_names

[alt_names] 
DNS.1 = *.pf9.localnet # must have for now
DNS.2 = *.localnet  # this and following values should be based on the DU FQDN
DNS.3 = *.pf9.localnet
DNS.4 = *.airctl-1-2662399-213.pf9.localnet

b. Create CA key and certs:

c. Remove passphrase from key

d. Add entries of CA key and cert to airctl.conf

e. Add CA cert to trust store:

If you want to just use external CA and let airctl generate the certs for DU, this is enough. If you want to generate certs for DU as well, you can continue with following steps.

f. Generate new key for DU and generate cert signing request:

g. Sign the cert using CA:

h. Remove passphrase for key

i. Add entries for key/cert in airctl.conf

Additional Information

NOTES:

  1. There is no impact if we do not use the custom certs, Platform9 will generate self signed certs if no user-provided certs are available.

  2. It is possible to implement custom certs in the current deployment by updating the deployment with the custom certs using https://platform9.com/docs/v5.7/PEC/custom-fqdn-and-certificates#renewing-certsarrow-up-right

Last updated