Configuring secure sockets

You can configure Change Management Server (CM Server) to support the Secure Sockets Layer (SSL) protocol to provide secure communication between CM Server and the ClearCase Remote Client (CCRC), or between CM Server and ClearQuest Web.

About this task

The current version of CM Server does not support OpenSSL. If you are upgrading a product that uses CM Server and you want to use previously created OpenSSL certificates, see Converting Open SSL certificates to IBM SSL certificates. You do not need to perform any of the next steps if you perform the conversion.

The following variable is used in path names in this topic:
RATIONAL_COMMON
Directory where Rational common files are installed

Procedure

  1. Uncomment the statement Include conf/ssl.conf in the file %RATIONAL_COMMON%\IHS\conf\httpd.conf.
  2. If you have not created the files %RATIONAL_COMMON%\IHS\key.kbd and %RATIONAL_COMMON%\IHS\key.sth, do so by using the IBM HTTP Server Key Management utility. For more information, see Creating HTTP server keys and help for IKeyMan.
  3. Create the IBM SSL certificate. See Creating a self-signed certificate for the HTTP Server. For information about creating a new certificate request to send to the certificate authority, see the help for IKeyMan.
  4. See Forcing an SSL connection with CM Server to force the processing of non-SSL requests as SSL requests.

Feedback