r15 - 2023-12-01 - 07:14:40 - ShradhaSrivastavYou are here: TWiki >  Deployment Web > DeploymentAdminstering > ConfigureCACertificates

Configure CA and Self-Signed Certificates in Liberty and IHS for ELM Applications new.png

Authors: ShradhaSrivastav, BharathRao
Build basis: ELM 6.x - 7.0.2 Sr1

Understanding SSL Certificates

All applications which run on HTTPS via the web require a Security Certificate, or Public Key Certificate. This is used to validate that the data is coming from a trusted source. The security certificate bundled with the Jazz Team Server and ELM applications is signed to localhost. As soon as the application is accessed with a URL other than localhost (for example, hostname or IP address), the browser will present the following errors:

  • The security certificate presented by this website was not issued by a trusted certificate authority.
  • The security certificate presented by this website was issued for a different website's address.
These errors occur because:
  • The security certificate was self-signed, meaning that the server being accessed created the certificate, and
  • The security certificate was created for localhost, and you are accessing the server using a different hostname, IP address or the appropriate Public URI.

In order to resolve these errors, you can:
  • Purchase a certificate from a well-known trusted Certificate Authority and install it.
  • If you do not need encryption, configure the server for HTTP rather than HTTPS access.
  • Configure the browser to ignore or accept this invalid certificate

In this article we will provide a guide on how to configure CA Certificate purchased from well-known Authority or internal CA certificate.

Using IKEYMAN (Graphical User Interface)

Create Keystore (Optional, if existing keystore is not used)

  1. Open ikeyman.exe, Key Database File -> New
  2. Select any Type
  3. Provide File name and path to the file


Update server.xml (Only for Liberty) to point to new key store (Optional, only if new keystore is created)

  1. Update server.xml located at JazzTeamServer\server\liberty\servers\clm to point to new database file, type and password
  2. If type Selected while creating keystore is pk12 Type will be PKCS12, for jks Type will be JKCS
  3. Restart the server for changes to take effect


To Create A Self-Signed Certificate

  1. Open ikeyman (GUI) utility located at JazzTeamServer\server\jre\bin
  2. Key Database File -> Open -> Browse to keystore file, enter password to open the file
  3. Click Create -> New Self Signed Certificate and fill the required details
  4. Restart server for changes to take effect




To Configure A CA Certificate

Generate certificate Request

  1. Open the Keystore database file using ikeyman
  2. Click Create -> New Certificate request and fill the necessary details


  3. 7.png

Send the certificate request generated to CA authority

Receive Certificate and Add it to Keystore

  1. Open the Keystore database file using ikeyman
  2. Select Personal Certificates
  3. Click Receive -> Browse to the certificate received




Add Intermediate and Root certificate

(In case the Intermediate certificate is not included in the certificates received or CA is not a trusted (internal CA) , add them explicitly in Signers)
  1. Open the Keystore database file using ikeyman
  2. Switch to Signer Certificates
  3. Click Add -> Browse to Intermediate/Root certificate
  4. Enter a label in dialog box


Installation Paths for each component will be:

   For CLM Liberty use ikeycmd
   IBM HTTP Server use gskcmd

Create Keystore (Optional, if existing keystore is not used)

ikeycmd -keydb -create -db .kdb -pw  -type cms -expire  -stash .sth


Update server.xml (Only for Liberty) to point to new key store (Optional, only if new keystore is created)


Create Self-Signed certificate

ikeycmd -cert -create -db  -pw  -label 


Configure CA Certificate

  1. Generate certificate Request
ikeycmd -certreq -create -db .kdb -pw  -label 


  1. Send the certificate request generated to CA authority
  2. Receive Certificate and Add it to Keystore
ikeycmd -cert -receive -file  -db .kdb -pw  -format  -default_cert 


Note: If the CA that issuing your CA-signed certificate is not a trusted CA in the key database, store the CA certificate first and designate the CA as a trusted CA. Then you can receive your CA-signed certificate into the database. You cannot receive a CA-signed certificate from a CA that is not a trusted CA. To add CA to trust store, follow Intermediate and Root certificate section

Intermediate and Root certificate

In case of chain-intermediate certificate add then to Signers in keystore
ikeycmd -cert -add -db .kdb -pw  -label 


Additional commands

To verify that the signer certificates were imported successfully, run the following command:

./gskcmd -cert -list CA -db .kdb -pw 

Display a list of certificates in a key database
./gskcmd -cert -list -db .kdb -pw 


If the existing certificate in keystore is expired and new certificate request needs to be created, you can use below command to recreate the request which will use details from previously created certificate request

./gskcmd -certreq -recreate -type cms -db .kdb -pw  -label 

Note: The label needs to be same as original certificate request which can be found using list command

./gskcmd -certreq -recreate -type cms -db ihskeys.kdb -pw secret -label caelm -target newreq.arm
Reference https://www.ibm.com/support/knowledgecenter/SSEQTJ_9.0.5/com.ibm.websphere.ihs.doc/ihs/rihs_ikeycmdsyn.html

For Chrome In case of using Internal CA when accessing the application in Chrome it still displays the certificate warning because of stringent security feature added by chrome, to fix that follow the steps from below link https://www.techrepublic.com/article/how-to-resolve-ssl-certificate-warnings-produced-by-the-latest-chrome-update/

Related topics: Deployment web home, Deployment web home

External links:

Additional contributors: ShradhaSrivastav, BharathRao
Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r15 < r14 < r13 < r12 < r11 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.