Agent Guides › Web Agent Guide › Configure Reverse Proxy Servers › How Reverse Proxy Servers Work with SiteMinder › SiteMinder Reverse Proxy Deployment Considerations › How to Configure An Apache Reverse Proxy Server

How to Configure An Apache Reverse Proxy Server

To configure an Apache-based reverse proxy server with SiteMinder, use the following process:

1. Update the settings of the following parameters for any Apache Web Agents located behind the Apache reverse proxy server:
   1. Set the ProxyAgent value to yes to indicate that this Agent is acting as a reverse proxy Agent.
   2. Set ProxyTimeout parameter to a value (in seconds).

      The reverse proxy uses this value to time out the requests it makes to the Web Agent deployed behind it.

   3. Edit the BadURLChars parameter by removing all occurrences of the following value from the list:

      %
      

   4. (Optional) Enable the ProxyTrust parameter.

      By setting this parameter to yes, it instructs the Web Agent behind the proxy Agent to trust the session information sent from the proxy Agent. and not to re-validate it. Enabling this parameter makes communication more efficient because only one call is made from the proxy Agent to the Policy Server. The Agent behind the proxy does not have to contact the Policy Server.

   5. Set the httpsports parameter to indicate to the Apache server which port is set up for SSL.
2. Add the following directives to the httpd.conf file of your Apache Web server:

   ProxyPass

   Allows mapping of remote servers to the local server. The values in this directive use the following format:

   /local_virtual_path partial_URL_of_remote_server

   Example: ProxyPass /realma/ http://server.example.org/realma/

   ProxyPassReverse

   Allows adjustment of the location header by the Apache server on HTTP redirect responses. The values in this directive use the following format:

   /local_virtual_path partial_URL_of_remote_server

   Example: ProxyPassReverse /realma/ http://server.example.org/realma/

   Note: For more information about directives, see the documentation for your web server.

3. Restart your Apache web server.