Nov 05, 2019 Method 2 Generate the certificate using the mydomain csr and key along with the CA Root key $ openssl x509 -req -extfile. Configuring ssl requests with SubjectAltName with openssl With Multiple Domain Certificates you can secure a larger number of domains with only one certificate. Subject Alternative Names are a X509 Version 3 (RFC 2459) extension to allow an SSL certificate to specify multiple names that. The openssl command doesn’t provide a way to include extensions like the subjectAltName without writing a config file first. I have written a simple utility that does it all automatically. How to Generate and Update SSL SAN Certificate in Linux. March 28, 2018 June 17. 6.1 To generate the private Key file for CERT generation. 5 Ways to find Memory size in Linux. December 24, 2019 December 24, 2019. Steps to Install Oracle Database 12c Release 2 in Redhat Linux 7.5.

The software described in this documentation is either no longer supported or is in extended support.
Oracle recommends that you upgrade to a current supported release.

1.8.5 SSL SecurityWarning: Certificate has no `subjectAltName`

When you configure a Ceph Object Gateway instance and enable SSL you must create an SSL certificate. If the certificate does not have the v3 extension enabled and the subjectAltName set within the certificate, a warning message is displayed when a client such as the Swift client attempts to access the gateway:

If a subjectAltName extension of type dNSName is present, this is used as the identity. Otherwise, the Common Name field in the Subject field of the certificate is used. Although the use of the Common Name is existing practice, it is deprecated and Certification Authorities are encouraged to use the dNSName instead.

To prevent the warning from appearing at all, do the following:

In the working directory where you are generating the key and certificate, create a copy of the template OpenSSL configuration file:
Modify the configuration file template at ./openssl.cnf and make the following changes:
- In the section [ req ] make sure that the following line is uncommented and not preceded with a # character:
- In the section [ v3_req ], add the following line to the end of the parameters in this section:
- Add a section to the end of the configuration file:
  Replace hostname.example.com with the fully qualified domain name for the host that you are creating the certificate for.
Generate your certificate key, as normal:
Use the certificate key and the new openssl.cnf file to create a Certificate Signing Request (CSR):
You may either use the generated CSR to obtain a signed certificate from a recognized Certificate Authority (CA). Or, for testing purposes, you may use this to generate a self-signed certificate as follows:
- Create a new configuration file, v3.cnf, that can host the information for the v3 requirements. Edit it to contain the following lines:
- Run the following OpenSSL command to generate a self-signed certificate using the CSR and your local key:
Copy the key, CSR and certificate to the usable location on the host:
Create a single PEM file containing both the key and certificate, that can be used by the Ceph Object Gateway when it is started:

(Bug 24424028)

The machine SSL certificate is used by the reverse proxy service on every management node, Platform Services Controller, and embedded deployment. Each machine must have a machine SSL certificate for secure communication with other services. You can replace the certificate on each node with a custom certificate.

Before you start, you need a CSR for each machine in your environment. You can generate the CSR using vSphere Certificate Manager or explicitly.

To generate the CSR using vSphere Certificate Manager, see Generate Certificate Signing Requests with vSphere Certificate Manager (Custom Certificates).
To generate the CSR explicitly, request a certificate for each machine from your third-party or enterprise CA. The certificate must meet the following requirements:
- Key size: 2048 bits or more (PEM encoded)
- CRT format
- x509 version 3
- SubjectAltName must contain DNS Name=<machine_FQDN>
- Contains the following Key Usages: Digital Signature, Non Repudiation, Key Encipherment

See also VMware Knowledge Base article 2112014, Obtaining vSphere certificates from a Microsoft Certificate Authority.

Linux Generate Ssl Key With Subjectaltname Windows 7

Procedure

Start vSphere Certificate Manager and select option 1.
Select option 2 to start certificate replacement and respond to the prompts.
vSphere Certificate Manager prompts you for the following information:
- Password for administrator@vsphere.local.
- Valid Machine SSL custom certificate (.crt file).
- Valid Machine SSL custom key (.key file).
- Valid signing certificate for the custom machine SSL certificate (.crt file).
- If you are running the command on a management node in a multi-node deployment, IP address of the Platform Services Controller.

Depending on your environment, you might have to replace additional certificates explicitly. Ssh generate new private key.

Linux Generate Ssl Key With Subjectaltname Key

If company policy requires that you replace all certificates, replace the vmdir root certificate. See Replace the VMware Directory Service Certificate
If you are upgrading from a vSphere 5.x environment, you might have to replace the vCenter Single Sign-On certificate inside vmdir. See Replace the VMware Directory Service Certificate in Mixed Mode Environments

1.8.5 SSL SecurityWarning: Certificate has no subjectAltName

Linux Generate Ssl Key With Subjectaltname Windows 7

Procedure

Linux Generate Ssl Key With Subjectaltname Key

1.8.5 SSL SecurityWarning: Certificate has no `subjectAltName`