NetWorker: Generazione CSR per SSL con SAN "Subject Alternative Name"

1. Creare un file su qualsiasi host Linux.

vi server_cert.cnf

2. Incollare i seguenti contenuti in server_cert.cnf di NetWorker.

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

[req_distinguished_name]
C   = 
ST  = 
L   = 
O   = 
OU  = 
CN  = 

[req_ext]
subjectAltName = @alt_names

[alt_names]
DNS.1 = 
DNS.2 = 
DNS.3 =
IP.1 =
IP.2 =
email.1 = 

3. Una volta creato il modello precedente, inserire le informazioni specifiche dell'ambiente. Contattare l'amministratore di dominio se è necessaria assistenza per la generazione della CSR. 

Country (C): The two-letter ISO code(* see link below)  for the country where the organization is located.

State/County/Region (ST): The state/region where the organization is located.

Locality (L): The city where the organization is located.

Organization Name (O): Usually the legal name of a company or entity and should include any suffixes such as Ltd., Inc., or Corp.
Organizational Unit (OU): Internal organization department/division name.

Common Name (CN): The fully or qualified domain name (FQDN) of the server based on the hostname available on the nsrla of the host.

Clarified SAN Guidance : It is important to include the FQDN as DNS.1. Add the short hostname and any other aliases or IP addresses as needed to cover all valid ways the host may be accessed. 

DNS.1: Mandatory. Always set to the full FQDN of the host (e.g., server.company.com).

DNS.2: Recommended. Short hostname (e.g., server).

DNS.3: Optional. Additional FQDN, short name, or IP address — use this for aliases, VIPs, or any other name that might resolve to the same server.

email.x: Optional. Include if required by your CA or if you want the cert to bind to an email identity.

IP.x: Optional. Use IP.x only when you want clients to connect directly to the IP and still trust the cert. If you don’t add IP.x and someone connects to https://192.168.1.10 → the SSL check will fail because the cer

* Il codice ISO di due lettere per il paese o la regione in cui si trova l'organizzazione.

Aggiungere o rimuovere voci DNS.x e IP.x in base alle esigenze.

Esempio:

[req]
distinguished_name = req_distinguished_name
req_extensions = req_ext
prompt = no
[req_distinguished_name]
C   = US
ST  = Texas
L   = Round Rock
O   = Dell Technologies Inc.
OU  = Data Protection Team
CN  = server.fqdn.example.com    # Common Name - must match primary FQDN

# ================================
# Extensions for SAN
# ================================
[ req_ext ]
subjectAltName = @alt_names

[ alt_names ]
# DNS.1: Mandatory — fully qualified domain name (FQDN)
DNS.1 = server.fqdn.example.com

# DNS.2: Recommended — short hostname (without domain)
DNS.2 = servername

# DNS.3: Optional — additional FQDN, short name, or IP address
DNS.3 = server.alias.example.com

# Optional: include email if needed
#IP.1 = 192.1xx.1.10               # Literal IP address
#IP.2 = 10.1.1.5                   # Another IP if needed
#email.1 = admin@example.com

4. Eseguire il comando riportato di seguito per generare la CSR e la chiave privata in base alle informazioni aggiunte nel file server_cert.cnf.

#openssl req -new -newkey rsa:4096 -nodes -keyout new_server.key -out new_server.csr -config server_cert.cnf

5. La CSR viene inviata a una CA per la firma. 

NetWorker: Il servizio NMC GST si avvia, quindi si arresta immediatamente dopo la sostituzione di cakey.pem