IBM WebSphere V5.0 Security - CGISecurity

publicly circulating root certificate authorities (CAs). In this case, optionally
delete all of the CA trusted signer certificates.
7. From the ikeyman menu, select Create -> New Self-Signed Certificate to
create a new self-signed certificate key pair. The following options then need
to be specified; you may choose to complete all of the remaining fields for the
sake of completeness:
Key Label: WASplugin
Version: X509 V3
Key Size: 1024
Common Name: websrv01.itso.ibm.com
Organization: IBM
Country: US
Validity Period: 365
Click OK when you are finished.
8. Extract the public self-signed certificate key, as this will be used later by the
embedded HTTP server peer to authenticate connections originating from the
plug-in.
9. Select Personal Certificates in the drop-down menu and select the
WASplugin certificate that just was created.
10.Click the Extract Certificate button, ensuring that WASplugin remains
selected. Extract the certificate to a file:
Data type: Base64-encoded ASCII data
Certificate file name: WASpluginPubCert.arm
Location: c:\IBMHttpServer\conf\keys (or the directory of your choice)
Click OK when you are finished.
11.Close the key database and quit ikeyman when you are finished.
Generating a self-signed certificate for the Web Container
The following steps will show how to generate a self-signed certificate for the
WebSphere Web Container.
1. Launch the IBM JKS capable ikeyman version that ships under the
WebSphere bin directory. On Windows systems, start it with the ikeyman.bat
command, on UNIX systems run the ikeyman.sh script.
2. From the ikeyman menu select Key Database File -> New.
304 IBM WebSphere V5.0 Security Handbook