TPP · Trust Framework · Certificates

Certificates with a SAN 2 min read

The Subject Alternative Name (SAN) extension is required on server-side certificates — specifically the server transport certificates LFIs present on their Ozone Connect endpoints.

This page applies to LFI server certificates

The Subject Alternative Name (SAN) extension is required on server-side certificates — specifically the server transport certificates LFIs present on their Ozone Connect endpoints. TPPs generating client certificates (transport, signing, or encryption) do not add a SAN; they set the CN to their application's Client ID instead. See Keys and Certificates for client certificate requirements.

01 Adding a Subject Alternative Name (SAN)

Inline -addext on the CSR

Modern browsers and certificate authorities no longer rely on the Common Name (CN) field for hostname validation on server certificates. Instead, they require the Subject Alternative Name (SAN) extension specifying the DNS hostnames the certificate is valid for — in this context, the hostname of the LFI's Ozone Connect server.

To include a SAN directly in the CSR without needing a separate config file, you can use the -addext option:

openssl with SANbash
openssl req -new -newkey rsa:2048 -nodes \
-out ...-opf_uae_server_transport.csr \
-keyout ...-opf_uae_server_transport.key \
-subj "/C=AE/O=Organisation Name/OU=b345..." \
-sha256 \
-addext "subjectAltName=DNS:some.hostname.com"

In this example, some.hostname.com will appear in the SAN extension of the CSR.

02 Why SAN Instead of CN

Server certificates rely on SAN, not CN, for hostname validation

Historically, SSL/TLS server certificates included the Common Name (CN) to specify the hostname. However:

  • CN is deprecated — as of RFC 2818 and subsequent updates, browsers and certificate authorities have stopped using CN for hostname validation on server certificates.
  • SAN is mandatory — the Subject Alternative Name is now the authoritative field for hostname checking.
  • Multiple hostnames — SAN supports multiple DNS names (and IP addresses), whereas CN supports only one.

For server certificates, hostname validation relies solely on the SAN. Including a CN is optional and depends on the LFI's setup; when present, it is not used for hostname validation.

03 OpenSSL Version Support

-addext requires OpenSSL 1.1.1 or newer

The -addext option was introduced in OpenSSL 1.1.1 (released September 2018). If you are using OpenSSL 1.1.1 or later, you can add SANs inline as shown above.

On older versions of OpenSSL, you will need to use an external configuration file (openssl.cnf) to include SANs.