IBM WebSphere V5.0 Security - CGISecurity

Configuring the Interceptor
In order to make an inteceptor configurable, it is necessary for it to extend
com.ibm.websphere.security.WebSphereBaseTrustAssociationInterceptor.
Three methods must be implemented.
►
►
►
public int init(java.util.Properties)
Accepts a Properties object which contains the necessary interceptor
configuration information.
public int init(String)
Accepts a file name for a file that contains the necessary interceptor
configuration information. The format of the properties file is specified in the
Infocenter.
public void cleanup()
Prepares the Interceptor for termination.
Configuring WebSphere to use the Interceptor
Once the Interceptor has been installed and the trust association is configured,
the application server may receive requests from the reverse proxy server. The
authentication method used must be LTPA and authentication cannot be
delegated to a reverse proxy server if the user registry is LocalOS. For
information regarding the configuration of WebSphere for LTPA, refer to 10.6,
“LTPA” on page 250 and for Trust Association Interceptors, refer to 12.4.1,
“Single Sign-On with WebSEAL” on page 386.
Note: The InfoCenter provides information regarding the setup of Tivoli
WebSEAL as a reverse proxy and the application server includes an
implementation of the TAI for this product. Also, refer to 12.5.1, “Tivoli
WebSEAL” on page 412.
Custom Trust Association Interceptor
This section will provide information on how to develop your own Trust
Association Interceptor, how to configure a new Interceptor for WebSphere and
finally how to test it.
Important: The custom Trust Association Interceptor here is only provided to
show how to develop a custom Interceptor. The Interceptor provided here is
not secure enough to use in any real environment.
Developing the custom Trust Association Interceptor
The Trust Association Interceptor (TAI) for this book was developed using the
WebSphere Studio.
Chapter 8. Programmatic security 191