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.

10.9.3 Using the Java keytool<br />

Another way to create self-signed keys and certificate requests is to use the Java<br />

keytool command line utility that comes with the Java Development Kit from Sun.<br />

The Java keytool utility gives your more flexibility to create your own customized<br />

certificate request with the DN (Distinguished Name) of your choice.<br />

For more information about Java keytool, refer to the documentation at:<br />

http://java.sun.com/j2se/1.3/docs/tooldocs/tools.html#security<br />

10.9.4 Configuring <strong>WebSphere</strong> to use a key store<br />

Once a key store has been configured, either by creating a self-signed certificate<br />

or by creating a certificate request and importing the reply, <strong>WebSphere</strong> can be<br />

configured to make use of the certificate. <strong>WebSphere</strong> will use the certificate in<br />

order to establish a secure connection with a client via SSL.<br />

Note: Before making changes to the sas.client.props file, it is recommended<br />

that you make a copy for restoration purposes if the need arises.<br />

It is necessary to define an SSL configuration, which will be used to determine<br />

how SSL connections are established with the appropriate <strong>WebSphere</strong><br />

components.<br />

Using the Administrative Console<br />

The following steps will create a new SSL definition entry for <strong>WebSphere</strong> using<br />

the Administrative Console; follow the steps from 10.8.1, “SSL configurations” on<br />

page 259 using the values below:<br />

1. Enter WASV5IntSec as the Alias.<br />

2. Select the new WASV5IntSec link.<br />

3. Select Secure Socket Layer (SSL).<br />

4. Enter the location of the server's key file in the Key File Name text area:<br />

c:\<strong>WebSphere</strong>\Appserver\etc\WASV5ServerKeyFile.jks in this example .<br />

5. Enter the key file password in the Key File Password text area.<br />

6. Ensure that JKS is the selected Key File Format.<br />

7. Enter the location of the server's trust file in the Trust File Name text area, in<br />

our case: c:\<strong>WebSphere</strong>\Appserver\etc\WASV5ServerTrustFile.jks.<br />

8. Enter the trust file password in the Trust File Password text area.<br />

9. Ensure that JKS is the selected Trust File Format.<br />

276 <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!