IBM WebSphere V5.0 Security - CGISecurity

There should now be the four key stores called:
►
►
►
►
WASV5ServerKeyFile.jks
WASV5ServerTrustFile.jks
WASV5ClientKeyFile.jks
WASV5ClientTrustFile.jks
There should also be two extracted certificates called:
► WASV5IntSecPubCert.arm
► WASV5ClientSecPubCert.arm
10.9.2 Requesting a certificate signed by a CA
The ikeyman tool can be used to generate a certificate request. A certificate will
be required for the server and one for each client. The process documented
below is for the server’s key file although the process will be similar for every
certificate with only minor changes needed for each.
1. Launch the ikeyman tool. It may be started from the command line in the bin
directory as ikeyman.bat (on Windows platforms) or ikeyman.sh (on UNIX
platforms)
2. From the menu bar, select Key Database File -> New.
3. Ensure that the Key database type is set to JKS. This section will use the
following file names to represent the appropriate key stores
– WASV5ServerKeyFile.jks - server key file
– WASV5ServerTrustFile.jks - server trust file
– WASV5ClientKeyFile.jks - client key file
– WASV5ClientTrustFile.jks - client trust file
4. Enter WASV5ServerKeyFile.jks as the file name.
5. Enter the directory that will hold the key file as the location, in this case:
c:\WebSphere\Appserver\etc.
6. Click OK.
7. A password prompt will appear. Enter a password and repeat to confirm. This
password will be required to read from or write to this file in the future, so do
not forget it. The password strength is determined by the variety of the
characters used in the password
8. Click OK.
9. From the menu bar, select Create -> New Certificate Request.
Chapter 10. Administering WebSphere security 271