13.07.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS
  • No tags were found...

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 keytoolAnother way to create self-signed keys and certificate requests is to use the Javakeytool command line utility that comes with the Java Development Kit from Sun.The Java keytool utility gives your more flexibility to create your own customizedcertificate request with the DN (Distinguished Name) of your choice.For more information about Java keytool, refer to the documentation at:http://java.sun.com/j2se/1.3/docs/tooldocs/tools.html#security10.9.4 Configuring <strong>WebSphere</strong> to use a key storeOnce a key store has been configured, either by creating a self-signed certificateor by creating a certificate request and importing the reply, <strong>WebSphere</strong> can beconfigured to make use of the certificate. <strong>WebSphere</strong> will use the certificate inorder to establish a secure connection with a client via SSL.Note: Before making changes to the sas.client.props file, it is recommendedthat you make a copy for restoration purposes if the need arises.It is necessary to define an SSL configuration, which will be used to determinehow SSL connections are established with the appropriate <strong>WebSphere</strong>components.Using the Administrative ConsoleThe following steps will create a new SSL definition entry for <strong>WebSphere</strong> usingthe Administrative Console; follow the steps from 10.8.1, “SSL configurations” onpage 259 using the values below:1. Enter WASV5IntSec as the Alias.2. Select the new WASV5IntSec link.3. Select Secure Socket Layer (SSL).4. Enter the location of the server's key file in the Key File Name text area:c:\<strong>WebSphere</strong>\Appserver\etc\WASV5ServerKeyFile.jks in this example .5. Enter the key file password in the Key File Password text area.6. Ensure that JKS is the selected Key File Format.7. Enter the location of the server's trust file in the Trust File Name text area, inour case: c:\<strong>WebSphere</strong>\Appserver\etc\WASV5ServerTrustFile.jks.8. Enter the trust file password in the Trust File Password text area.9. Ensure that JKS is the selected Trust File Format.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!