IBM WebSphere V5.0 Security - CGISecurity

24.From the menu bar, select Key Database File -> Close. This will close the
current key store.
The server's trust file
To create the server’s trust file, repeat the first nine steps from “The server's key
file” on page 264 (up to clicking OK on the password prompt) with a file name of
WASV5ServerTrustFile.jks. It is not necessary to populate the trust file with any
certificates at this stage.
The client's key file
The client's key file provides a client certificate during the SSL connection
initialization. This certificate contains the identity of the caller that is not
necessarily restricted to establishing an SSL connection but may also be used
for authentication purposes at a J2EE level. The creation of this key file is very
similar to that of the server’s key file and so refer to “The server's key file” on
page 264 for details. The file name of the key file is WASV5ClientKeyFile.jks in
this sample, the certificate label is WASV5ClientSec and the extracted certificate
is WASV5ClientSecPubCert.arm. The client certificate can be added to the
server’s trust file.
1. Open WASV5ServerTrustFile.jks in ikeyman.
2. Select Signer Certificates from the Key Database Content drop-down menu.
3. Click Add.
4. Enter the details for the client certificate (WASV5ClientSecPubCert.arm).
5. Click OK.
6. Enter the label for the certificate which is WASV5ClientSec.
7. Click OK. The certificate should be added to the list of signer certificates.
8. Close the file.
The client's trust file
To create the client’s trust file, repeat the first nine steps from “The server's key
file” on page 264 (up to clicking OK on the password prompt) with a file name of
WASV5ClientTrustFile.jks. It will be necessary to add the server’s extracted
certificate as a signer certificate. The process for this is documented in “The
client's key file” on page 270”.
270 IBM WebSphere V5.0 Security Handbook