IBM WebSphere V5.0 Security - CGISecurity

publicly circulating root certificate authorities (CAs). In this case, optionallydelete all of the CA trusted signer certificates.7. From the ikeyman menu, select Create -> New Self-Signed Certificate tocreate a new self-signed certificate key pair. The following options then needto be specified; you may choose to complete all of the remaining fields for thesake of completeness:Key Label: WASpluginVersion: X509 V3Key Size: 1024Common Name: websrv01.itso.ibm.comOrganization: IBMCountry: USValidity Period: 365Click OK when you are finished.8. Extract the public self-signed certificate key, as this will be used later by theembedded HTTP server peer to authenticate connections originating from theplug-in.9. Select Personal Certificates in the drop-down menu and select theWASplugin certificate that just was created.10.Click the Extract Certificate button, ensuring that WASplugin remainsselected. Extract the certificate to a file:Data type: Base64-encoded ASCII dataCertificate file name: WASpluginPubCert.armLocation: 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 ContainerThe following steps will show how to generate a self-signed certificate for theWebSphere Web Container.1. Launch the IBM JKS capable ikeyman version that ships under theWebSphere bin directory. On Windows systems, start it with the ikeyman.batcommand, 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