You can use a Oracle iPlanet 7.0 web server as a reverse proxy with SiteMinder.
Note: The SiteMinder Agent Configuration wizard only modifies the default obj.conf file on the Oracle iPlanet (formerly Sun Java System) web server. To protect other instances or reverse proxy deployments with SiteMinder, copy the SiteMinder settings from the default obj.conf file to any respective instance_name-obj.conf files. For example, your web server created an obj.conf file when you installed it, but you later added a server instance named my_server.example.com. To protect resources on my_server.example.com with SiteMinder, copy the SiteMinder settings the wizard added from the obj.conf file to the my_server.example.com-obj.conf file.
Follow these steps:
Specifies the local and remote virtual paths using the following format:
NameTrans fn="map" from="local_virtual_path" name="reverse-proxy-/local_virtual_path" to="remote_virtual_path"
Example: NameTrans fn="map" from="/realma" name="reverse-proxy-/reamla" to="http://server.example.org/realma/"
Specifies the name of the local virtual path and the URL of the remote virtual path used in the NameTrans directive, using the following format:
<Object name="reverse-proxy-/local_virtual_path">
Route fn="set-origin-server" server="http://remote_server_URL:port"
</Object>
Example: <Object name="reverse-proxy-/realma">
Route fn="set-origin-server" server="http://server.example.org:port"
</Object>
Specifies the partial path that is given to the server by the client.
Example: <Object ppath="http:*">
Service fn="proxy-retrieve" method="*"
</Object>
The reverse proxy is configured.
For users who require a more sophisticated reverse proxy solution, CA SiteMinder SPS provides the following benefits over the Apache or Oracle iPlanet-based SiteMinder Reverse Proxy Agent:
CA SiteMinder SPS introduces a new layer in the traditional SiteMinder architecture. This layer forwards or redirects all requests to destination servers in the enterprise.
When CA SiteMinder SPS processes a request, the URL requested by the user is preserved in an HTTP header variable named SM_PROXYREQUEST. Other applications that require the original URL requested by a user before CA SiteMinder SPS proxied the request can use this header.
Copyright © 2012 CA.
All rights reserved.
|
|