Using the Tivoli Access Manager plug-in

A Caching Proxy plug-in is provided with Tivoli Access Manager (formerly Tivoli Policy Director) that enables Caching Proxy to use Access Manager for authentication and authorization. This plug-in makes it possible for an enterprise that uses Access Manager for Web access control to add Edge technology without having to duplicate work by setting up separate authorization schemes for the proxy server.

For additional information about Tivoli Access Manager, view the product Web site at http://www.ibm.com/software/tivoli/products/. For information about software and hardware requirements and about installing the Access Manager plug-in, refer to the documentation provided with Tivoli Access Manager.

Note:
The Tivoli Access Manager plug-in may not be supported on Red Hat Linux. Contact Tivoli for current support information on Linux platforms.

Configuration

A setup script for Caching Proxy is provided with the Access Manager plug-in.

Steps to take before using the configuration script

Before running the script, do the following:

Using the configuration script

The set up script is named wslconfig.sh and it is provided in the /opt/pdweb-lite/bin/ directory. Enter the Access Manager administrator ID and the LDAP administrator name when prompted.

The configuration script automatically performs the following steps:

Starting Caching Proxy and Access Manager plug-in

After configuring the proxy server and the Access Manager plug-in, use the command wslstartwte instead of ibmproxy start to start the proxy server. The wslstartwte command automatically loads environment variables that the Access Manager plug-in requires in order to initialize. If you do not use wslstartwte when starting the proxy server, error messages are displayed about the Access Manager plug-in. The corresponding stop command, ibmproxy stop, is still valid when the plug-in is used.