After installing the server, take these quick steps to enable basic security. Basic security allows your server to handle secure sockets layer (SSL) requests. SSL ensures that data transferred between a client and a server remains private.
This Quick Start example shows you how easy it is to set up secure network connections using the server's Key Management Utility (IKEYMAN) and setting some configuration directives.
JDK 1.1.6 ships with IBM WebSphere Application Server and is also available from the IBM Java JDK Web site. .
It is not necessary to reinstall any components you selected during the original installation.
Use the server's Key Management Utility (IKEYMAN) to create a new key database and specify a stashfile, a stashed password for that key database.
Note: If you do not use the default key database name, key.kdb, you must update the KeyFile directive in your configuration file.
Leave IKEYMAN running to create or import a certificate.
Use the server's Key Management Utility (IKEYMAN) to create a new key public-private key pair and certificate request.
Start a Web browser and enter the URL of the CA from
whom you want to obtain the certificate. To send your certificate, follow the
instructions provided by the CA. In this example, a request will be sent to
a CA that is already designated as a trusted root CA on the server.
Note: It usually takes two to three weeks to get a certificate from a well-known trusted CA. While you are waiting for the CA to process your certificate request, you can use IKEYMAN to create a self-signed server certificate to enable SSL sessions between clients and the server.
Use the server's Key Management Utility (IKEYMAN) to create a self-signed server certificate. I LEFT OFF HERE.
HostName your_host_name SSLEnable Keyfile /usr/lpp/HTTPServer/keys/keyfile.kdb
To enable changes to take effect, you need to restart the server. More is needed here.