How do I get intermediate certificate from root CA?

How do I get intermediate certificate from root CA?

Intermediate CA:

  1. Under PKI Management select Certificate Authorities.
  2. Select Add Certificate Authority.
  3. Choose Intermediate CA under Type.
  4. Select the corresponding Root CA under Certificate Authority.
  5. Choose your desired setting under Generate Via.
  6. Choose a name and expiration date then save.

How do I get an intermediate certificate authority?

Create Intermediate CA Certificates

  1. Create an OpenSSL configuration file called ca_intermediate.
  2. Generate the private key using a strong encryption algorithm such as 4096-bit AES256.
  3. Create a signing request.
  4. Sign the intermediate signing request with the root CA certificate.

How to verify a certificate chain using OpenSSL verify-stack?

Root Cert is a self signed certificate, Intermediate Certificate is signed by Root and User by Intermediate. Now I want to verify if a User Certificate has its anchor by Root Certificate. the validation is ok. In the next step I validate the User Cert with

How to create certificate chain with OpenSSL create certificate bundle?

To openssl create certificate chain (certificate bundle), concatenate the intermediate and root certificates together. In the below example I have combined my Root and Intermediate CA certificates to openssl create certificate chain in Linux. We will use this file later to verify certificates signed by the intermediate CA.

Where to find certificate database in OpenSSL CA?

The index.txt file is where the OpenSSL ca tool stores the certificate database. Do not delete or edit this file by hand. It should now contain a line that refers to the intermediate certificate. Next openssl verify intermediate certificate against the root certificate. An OK indicates that the chain of trust is intact.

How is the root CA used in OpenSSL?

The root CA is only ever used to create one or more intermediate CAs, which are trusted by the root CA to sign certificates on their behalf. This is best practice. It allows the root key to be kept offline and unused as much as possible, as any compromise of the root key is disastrous.