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...

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

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

The file used by a Java client to refer to a key store is the SAS properties file.Refer to “The sas.client.props file” on page 104 for details on the client SAS file.The <strong>WebSphere</strong> server, on the other hand, stores the key store information in therepository and the key stores are referred to in the security.xml file. Therefore, allserver-side configuration should be performed via the administration tools, suchas the Administrative Console.10.9.1 Generating a self-signed certificateThe process for creating a self-signed certificate is relatively straightforward. Anunderstanding of public/private key pairs and of PKI will be useful. The result ofthis process is a key store that will replace the temporary key store provided by<strong>WebSphere</strong>, on both server and client side.The server's key fileThe following steps will describe how to generate a new self-signed certificatewith the <strong>IBM</strong> ikeyman utility.1. Launch the ikeyman tool. It may be started from the command line in the bindirectory as ikeyman.bat (on Windows platforms) or ikeyman.sh (on UNIXplatforms).264 <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!