Your organization uses an in-house or commercial certificate authority (CA) which will be signing the appliance certificate for HTTPS access to the user interface. The keytool utility is limited in how it can create and import private keys into keystore files, making it difficult to properly setup a trust chain within the keystore used by RSA Identity Governance & Lifecycle when using CA signed certificates.
The steps in this article include how to:
Generate a keypair using openSSL.
Generate a certificate signing request (CSR) using that keypair in openSSL that you will give to your CA, who will return to you a signed certificate, a root CA certificate, and zero or more intermediate CA certificates which form the signing chain.
Combine all certificates into one file in their chaining order by copying the contents of each certificate into a new file.
Import the keypair and cert chain into a new keystore using Keystore Explorer.
Save the new keystore, backup the existing keystore, and replace the existing keystore with the new keystore.
Execute the commands below as the root user.
To generate a keypair you can use openSSL. There are many options available for generating keys, but here is a simple example:
This will generate a CSR based on the keypair generated in step 1.
Send the CSR generated in step 2 to your CA to have it signed. he CA will return to you a certificate for the host (end-point) as well as a root CA certificate and possibly some intermediate CA certificates. Typically these certificates will be in PEM format (base-64 encoded DER), with a file extension of .pem, .cer, .crt, or possibly others. For the purpose of this RSA Knowledge Base Article we will assume the CA returns to you a certificate named host-certificate.cer.
Note that each certificate provided by the CA forms a trust chain that represents the signing order in which the CA signed each certificate. This chain is of the form root CA certificate > zero or more Intermediate CA certificate(s) > Host certificate (referred to as end-point or leaf). There may not be intermediate CA certificates, but if there are, they must be included in the chain in the correct order. We must copy the contents of each certificate into a new file, which we will call chain-certificate.pem, in the order in which they signed each other. If you open each certificate in a text editor, you will find the certificate data is wrapped in a BEGIN and END header/footer as illustrated here:
In order to build the chain file (chain-certificate.pem), copy the contents of the certificate file, including the header and footer lines, into a new file. The first item in that new file should be the contents of the root CA certificate, followed by the first intermediate certificate, followed by any other intermediate certificates, and then lastly, the host certificate. For example, the chain file for a certificate signed by a CA using two intermediate certificates would look something like this:
If in doubt as to the order in which certificates were signed, the certificates can be examined (double click in Windows) and the subject and issuing fields inspected. The issuing field of the certificate will match the subject field of the certificate which signed it. Root CA certificates will be self-signed, meaning the issuing and subject fields will match. When this step is completed, you will have a number of certificate files provided by your CA, the newly created chain-certificate.pem, and the host-key.pem file generated in step 1 which contains the private key .
Download and install Keystore Explorer, if you haven't already. Keystore Explorer is a free, open-source, GUI replacement for the Java command-line utility keytool. It overcomes some of the limitations of keytool, such as the ability to import public/private key-pairs. To use Keystore Explorer:
Run Keystore Explorer.
When prompted, choose Create a new KeyStore.
Choose type JKS.
In the new keystore, choose Tools > Import Key Pair.
Select OpenSSL as the type.
If you encrypted your private key file with a password (as in step 1 by adding the -aes256 and -passout parameters), check the Encrypted Private Key box and enter the password used for the Decryption Password field.
For the OpenSSL Private Key File field, select the host-key.pem file generated in step 1.
For the Certificate(s) File, select the chain-certificate.pem created in step 4.
Click Import .
When prompted for an alias name, use server. There should now be an entry in the keystore named server. Verify that the chain order is correct by double-clicking the entry and inspecting the Certificate Hierarchy at the top of the details. The hierarchy should reflect the signing order, with the root CA certificate listed at the top, and the host certificate listed at the bottom, with any intermediate CA certificates listed imbetween.
Use File > Save as, and save the keystore as aveksa.keystore.
Perform the remaing steps as the oracle user:
Backup the existing keystore used byRSA Identity Governance & Lifecycle (note the ticks are true ticks, not apostrophes):
Replace the $AVEKSA_HOME/keystore/aveksa.keystore on the appliance with the one created in Keystore Explorer (setp 5).
Restart RSA Identity Governance & Lifecycle:
Ensure that the root CA certificate provided by your CA is trusted on the system from which you intend to access RSA Identity Governance & Lifecycle, then test the connection to ensure it validates the new certificate as trusted. This root CA certificate can also be set up to be trusted by the RSA Identity Governance & Lifecycle server by following the instructions in the RSA Identity Governance & Lifecycle Installation Guide for your version on how to import certificates into the Java cacerts file.
Note that to properly validate a host, the host certificate CN should match the address used to access the site. If the CN of the certificate does not match the name used to access the source, your browser will not be able to validate the certificate.