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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3. Set the following settings, then click OK when you are done:<br />

Key database file: JKS<br />

File name: WASWebContainer.jks<br />

Location: c:\<strong>WebSphere</strong>\Appserver\etc\ (or the directory of your choice)<br />

4. At the password prompt window, enter the password of your choice; for this<br />

sample, use password.<br />

5. Optionally, delete all the public Certificate Authority (CA) certificates under the<br />

Signer Certificates.<br />

6. From the ikeyman menu, select Create -> New Self-Signed Certificate.<br />

Specify the fields with your values; the followings were used fo this sample:<br />

Key Label: WASWebContainer<br />

Version: X509 V3<br />

Key Size: 1024<br />

Common Name: wassrv01.itso.ibm.com<br />

Organization: <strong>IBM</strong><br />

Country: US<br />

Validity Period: 365<br />

Click OK when you are finished.<br />

7. Extract the public self-signed certificate key, as it will be used later by the Web<br />

server plug-in peer to authenticate connections originating from the<br />

embedded HTTP server in <strong>WebSphere</strong>.<br />

8. Select Personal Certificates from the drop-down list, then select the<br />

WASWebContainer certificate that was just created.<br />

9. Click the Extract Certificate button, ensuring that WASWebContainer<br />

remains selected. Extract the certificate to a file:<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 />

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

Chapter 10. Administering <strong>WebSphere</strong> security 305

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

Saved successfully!

Ooh no, something went wrong!