The keystore file is a key database file that contains both public
keys and private keys. Public keys are stored as signer certificates while
private keys are stored in the personal certificates. The keys are used for
a variety of purposes, including authentication and data integrity.
Procedure
- Start
the iKeyman utility, if it is not already running.
- Open a new key database file by clicking Key Database File >
New from the menu bar.
- Select the Key Database Type: JKS (default),
PKCS12, JCEKS, or JCERACFKS (z/OS only). This is the key file format (or
the value of com.ibm.ssl.keyStoreType property in the sas.client.props file)
when you configure the SSL setting for your application.
- Select the Key Database Type: JKS (default),
PKCS12, JCEKS, JCERACFKS (z/OS only) or JCE4758RACFKS (z/OS only).
This is the key file format (or the value of com.ibm.ssl.keyStoreType property
in the sas.client.props file) when you configure the SSL setting
for your application.
- Type the file name and location. The full path of this key database
file is used as the key file name (or the value of the com.ibm.ssl.keyStore property
in the sas.client.props file) when you configure the Secure Sockets
Layer (SSL) setting for your application.
- Click OK to continue.
- Type a password to restrict access to the file. This password is
used as the key file password (or the value of com.ibm.ssl.keyStorePassword property
in the sas.client.props file) when you configure the SSL setting
for your application. Do not set an expiration date on the password or save
the password to a file; you must then reset the password when it expires or
protect the password file. This password is used only to release the information
stored by the key management utility during runtime.
- Click OK to continue. The tool displays all of the available
default signer certificates. These certificates are the public keys of the
most common certificate authorities (CAs). You can add, view or delete signer
certificates from this panel.
Results
A new SSL keystore file is created.
What to do next
Prepare keystore files for an SSL connection.
Specify the keystore
file in the configuration of WebSphere Application Server. Create a truststore
if one does not yet exist.