Skip to main content

Create a Multi-Domain Certificate Signing Request (CSR)

info
  • The Subject Alt Names are required in Google Chrome 58 and later, and is used to match the domain name and the certificate.
  • If the domain name is not listed in the certificate's Subject Alternative Names list, you'll get a NET::ERR_CERT_COMMON_NAME_INVALID error message.

1. Generate an OpenSSL CSR Config with your domain information

cat <<"EOF" | sudo tee /tmp/tls.conf > /dev/null
[req]
default_bits = 2048
default_keyfile = tls.key
distinguished_name = req_distinguished_name
req_extensions = req_ext
x509_extensions = v3_ca

[req_distinguished_name]
countryName = Country Name (2 letter code)
countryName_default = LK
stateOrProvinceName = State or Province Name (full name)
stateOrProvinceName_default = Western Province
localityName = Locality Name (eg, city)
localityName_default = Colombo
organizationName = Organization Name (eg, company)
organizationName_default = Example (Private) Limited
organizationalUnitName = organizationalunit
organizationalUnitName_default = Development
commonName = Common Name (e.g. server FQDN or YOUR name)
commonName_default = example.com
commonName_max = 64

[req_ext]
subjectAltName = @alt_names

[v3_ca]
subjectAltName = @alt_names

[alt_names]
DNS.1 = example.com
DNS.2 = *.example.com
DNS.3 = example.local
DNS.4 = *.example.local
EOF

2. Generate a Certificate Signing Request (CSR)

sudo openssl req -new -nodes -config /tmp/tls.conf -keyout tls.key -out tls.csr

3. References

  1. Create a Self-Signed Certificate for Nginx in 5 Minutes
  2. Establishing Trust to Your Cluster’s CA and Importing Certificates
  3. X509 Certificate Generator