Configuring RWP to use secure sockets

To provide secure communications between Web clients and RWP, you can configure RWP to support the IBM Secure Sockets Layer (IBM SSL) protocol. To do this,

  1. The current version of RWP no longer supports Open SSL. If you are upgrading a product that uses RWP and wish to use previously created Open SSL certificates, see Converting Open SSL certificates to IBM SSL to convert your existing certificates for use with IBM SSL. If you choose to perform the conversion, you do not need to perform any of the steps below. To create new certificates using IBM SSL, follow the rest of the steps below.
  2. Uncomment the Include conf/ssl.conf statement in httpd.conf
  3. If you have not created the files common/rwp/IHS/key.kbd and key.sth, do so using IKeyMan, the IBM utility for creating and managing SSL keys and key databases. Run IKeyMan from the common/rwp/IHS/bin directory. For more information, search http://www.ibm.com/ for the latest information on iKeyMan and then see Creating HTTP server keys.
  4. Next, create your certificate. See Creating a self-signed certificate for the HTTP server. For information about creating a new Certificate Request to send to Certificate Authority, see the Help for IKeyMan and scroll down to the section named How do I create a new Certificate Request.
  5. To force processing of non-SSL requests as SSL requests, using RWP, use the optional procedure Forcing an SSL connection using RWP.


Feedback