6409d62650
All TLS certificates are incorrectly generated in the 'certificates' role. The generated certificates don't contain both the 'X509v3 extensions' and 'X509v3 Subject Alternative Name' blocks at all. This change fixes the 'openssl x509' commands used to generate all the certificates to include the 'Subject Alternative Name'. Also, this change fixes both internal and external templates to constantly use alternative names as described in the RFCs [1] [2]. We use DNS Name in SAN extension only when 'kolla_internal_fqdn' or 'kolla_external_fqdn' is set. 1. https://datatracker.ietf.org/doc/html/rfc5280#section-4.2.1.6 2. https://datatracker.ietf.org/doc/html/rfc6125#appendix-B.2 Closes-Bug: #1935978 Change-Id: Ie5d82a2e4575bd74674ac38a042df49cfe7f74c9 Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
20 lines
400 B
Django/Jinja
20 lines
400 B
Django/Jinja
[req]
|
|
prompt = no
|
|
distinguished_name = req_distinguished_name
|
|
req_extensions = v3_req
|
|
|
|
[req_distinguished_name]
|
|
countryName = US
|
|
stateOrProvinceName = NC
|
|
localityName = RTP
|
|
organizationalUnitName = kolla
|
|
|
|
[v3_req]
|
|
subjectAltName = @alt_names
|
|
|
|
[alt_names]
|
|
{% if kolla_external_fqdn != kolla_external_vip_address %}
|
|
DNS.1 = {{ kolla_external_fqdn }}
|
|
{% endif %}
|
|
IP.1 = {{ kolla_external_vip_address }}
|