Web Agent Guides › Web Agent Configuration Guide › Configure Reverse Proxy Servers › How Reverse Proxy Servers Work with SiteMinder › SiteMinder Reverse Proxy Deployment Considerations

SiteMinder Reverse Proxy Deployment Considerations

Typically, when you deploy an Apache or Sun Java System reverse proxy Agent, a firewall is located between the Apache or Sun Java System Web Agent and the servers hosting the protected resources. The Policy Server should also be located behind the firewall.

The following illustration shows a SiteMinder reverse proxy deployment.

When deploying a SiteMinder reverse proxy Agent, consider the following:

• If a policy has been configured to return response attributes, the variables are sent to both the reverse proxy server and the backend web server on which the protected resource resides. When a request is made for a protected resource, the Policy Server first sends response attributes (CGI or HTTP variables) to the Agent on the Apache or Sun Java System server. The Agent then puts the response attributes in the request that is sent to the backend server.
• If any of the backend servers or protected applications provide their own authentication functionality, the authentication must be disabled. Disabling the backend authentication ensures that SiteMinder's authentication takes precedence.

  Important! When configuring the cache for the reverse proxy be aware that all cookies are cached, including the SMSESSION cookie. For assistance contact your Apache or Sun Java System vendor for support.