03.05.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Exchanging public certificates<br />

The following two sections will describe how to exchange certificates between<br />

the Web Container keystore and the Web server plug-in keyfile.<br />

In order to import the certificates into the keystores as described in the next two<br />

sections, you will have to copy over the two certificates and the extracted .arm<br />

files to both machines, the Web server, and the <strong>WebSphere</strong> server.<br />

1. Copy WASpluginPubCert.arm from the Web server machine to the<br />

<strong>WebSphere</strong> machine. The source directory in our case is c:\ihs\conf\keys,<br />

while the destination is: c:\<strong>WebSphere</strong>\Appserver\etc.<br />

2. Copy WASWebContainerPubCert.arm from the <strong>WebSphere</strong> machine to the<br />

Web server machine. The source directory in our case is c:\was\etc, while the<br />

destination is: c:\<strong>IBM</strong>HttpServer\conf\keys.<br />

Importing the certificate into the Web server plug-in keyfile<br />

1. On the Web server machine, launch the ikeyman utility that supports the CMS<br />

key database format.<br />

2. From the ikeyman menu select Key Database File -> Open and select the<br />

previously created key database file: WASplugin.kdb.<br />

3. At the password prompt window, enter the password then click OK.<br />

4. Select Signer Certificates from the drop-down list, then click the Add button.<br />

This will allow you to import the public certificate previously extracted from the<br />

embedded HTTP server/Web Container keystore.<br />

Data type: Base64-encoded ASCII data<br />

Certificate file name: WASWebContainerPubCert.arm<br />

Location: c:\<strong>WebSphere</strong>\Appserver\etc\<br />

Click OK when you are finished.<br />

5. You will be prompted for a label name by which the trusted signer public<br />

certificate will be known. Enter a label for the certificate: WASWebContainer.<br />

6. Close the key database and quit ikeyman when you are finished.<br />

Importing the certificate into the Web Container keystore<br />

1. On the <strong>WebSphere</strong> machine, launch the <strong>IBM</strong> JKS capable ikeyman version<br />

that ships under the <strong>WebSphere</strong> bin directory.<br />

2. From the ikeyman menu, select Key Database File -> Open and select the<br />

previously created WASWebContainer.jks file.<br />

3. At the password prompt, enter the password for the keyfile, then click OK.<br />

306 <strong>IBM</strong> <strong>WebSphere</strong> <strong>V5.0</strong> <strong>Security</strong> Handbook

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!