Configure the human resources HTTP Server to use SSL

Secure Sockets Layer (SSL) configuration for the human resources HTTP Server (powered by Apache) on iSeries™ A involves a number of tasks which vary depending on how your server is configured currently.

To configure the server to use SSL, follow these steps:

  1. Start the HTTP Server Administration interface.
  2. To work with a specific HTTP server, select these page tabs Manage —> All Servers —> All HTTP Servers to view a list of all configured HTTP servers.
  3. Select the appropriate server from the list and click Manage Details.
  4. In the navigation frame, select Security.
  5. Select the SSL with Certificate Authentication tab in the form.
  6. In the SSL field, select Enabled.
  7. In the Server certificate application name field, specify an application ID by which this server instance is known. Or, you can select one from the list. This application ID is in the form QIBM_HTTP_SERVER_[server_name], for example, QIBM_HTTP_SERVER_MYCOTEST. Note: Remember this application ID. You will need to select it again in the DCM.

You can learn more about the overall configuration needed for your HTTP Server when using SSL in the HTTP Server for iSeries Information topic, especially in an example called Scenario: JKL enables Secure Sockets Layer (SSL) protection on their HTTP Server (powered by Apache). This scenario provides all the task steps for creating a virtual host and configuring it to use SSL, including the following tasks:

  1. Set up of a name-based virtual host.
  2. Set up of a Listen directive for virtual host.
  3. Set up of the virtual host directories.
  4. Set up of password protection via basic authentication.
  5. Enablement of SSL for the virtual host

For additional information about configuring both current and future versions of the HTTP Server for iSeries, see the HTTP Server for iSeries topic.

When you complete the configuration for the HTTP Server to use SSL, you can use DCM to configure the certificate support that you need for SSL and client authentication.