Setting up a self signed certificate for the IBM HTTP Server configured as a Reverse Proxy
 Technote (troubleshooting)
 
This document applies only to the following language version(s):
Hebrew
 
Problem(Abstract)
How should self signed certificates be set up on the IBM® HTTP Server set up as a Reverse Proxy?
 
Cause
SSL handshake errors may occur if self signed certificates are not set up properly between the IBM HTTP Server set up as a Reverse Proxy and the target server.
 
Resolving the problem
To set up self signed certificates between a reverse proxy and a target server you must do the following.

1. Create a self signed certificate on the Proxy server using IKEYMAN.

2. Create a self signed certificate for the target server as well.

3. Extract the self signed certificate from the target server and add it to the signer certificates of the Proxy server.

4. If dual authentication is needed then also extract the self signed certificate of the Proxy server and add it to the signer certificates of the target server.

The above should work regardless of whether the proxy server is the HTTP Server or the WebSphere Edge Caching Proxy server.

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > IBM HTTP Server > SSL
Operating system(s): Windows
Software version: 6.1.0.3
Software edition:
Reference #: 1254064
IBM Group: Software Group
Modified date: Jan 22, 2007