Develop a custom interceptor for trust associations


If you are using a third party reverse proxy server other than Tivoli WebSEAL, provide an implementation class for the WAS interceptor interface to the proxy server.

  1. Define the interceptor class method using...

    ...which defines the following methods...

    • public boolean isTargetInterceptor (HttpServletRequest req) throws WebTrustAssociationException;.

      Determines whether the request originated with the proxy server associated with the interceptor. The implementation code must examine the incoming request object and determine if the proxy server forwarding the request is a valid proxy server for this interceptor. The result of this method determines whether the interceptor processes the request or not.

    • public void validateEstablishedTrust (HttpServletRequest req) throws WebTrustAssociationException;.

      Determines if the proxy server from which the request originated is trusted or not. This method is called after the isTargetInterceptor method. The implementation code must authenticate the proxy server. The authentication mechanism is proxy-server specific. For example, in WAS implementation for the WebSEAL server, this method retrieves the basic authentication information from the HTTP header and validates the information against the user registry used by WAS. If the credentials are invalid, the code throws the WebTrustAssociationException, indicating that the proxy server is not trusted and the request is to be denied.

    • public String getAuthenticatedUsername (HttpServletRequest req) throws WebTrustAssociationException;.

      Called after trust is established between the proxy server and WAS. WAS has accepted the proxy server authentication of the request and must now authorize the request. To authorize the request, the name of the original requestor must be subjected to an authorization policy to determine if the requestor has the necessary privilege. The implementation code for this method must extract the user name from the HTTP request header and determine if that user is entitled to the requested resource. For example, in WAS implementation for the WebSEAL server, the method looks for an iv-user attribute in the HTTP request header and extracts the user ID associated with it for authorization.

  2. Configure the interceptor.

    To make an interceptor configurable, the interceptor must extend...

    Implement the following methods...

    public int init(java.util.Properties props) The init(Properties) method accepts a java.util.Properties object, which contains the set of properties required to initialize the interceptor. All the properties set for an interceptor (by using the Custom Properties link for that interceptor or using scripting) is sent to this method. The interceptor then can use these properties to initialize itself. For example, in WAS implmentation for the WebSEAL server, this method reads the hosts and ports so that a request coming in can be verified to originate from trusted hosts and ports. A return value of 0 implies that the interceptor initialization is successful. Any other value implies that the initialization is not successful and the interceptor is ignored.

    Applicability of the following list

    If a previous implementation of the trust association interceptor returns a different error status you can either change your implementation to match the expectations or make one of the following changes...

    • Add the property in the trust association interceptor custom properties. Set the property to the value that indicates that the interceptor is successfully initialized. All of the other possible values imply failure. In case of failure, the corresponding trust association interceptor is not used.

    • Add the property in the trust association interceptor custom properties. Set the value of this property to true, which tells WAS to ignore the status of this method. If you add this property to the custom properties, WAS does not check the return status, which is similar to previous versions of WAS.

    public void cleanup (); This method is called when the appserver is stopped. It is used to prepare the interceptor for termination.

    public void setVersion String(s); This methods is optional. The method is used to set the version and is for informational purpose only. The default value is Unspecified.

    You must configure the following methods implemented by the custom interceptor implementation. This listing only shows the methods and does not include any implementation.

    import java.util.*;
    import javax.servlet.http.HttpServletRequest;
    public class myTAIImpl extends WebSphereBaseTrustAssociationInterceptor
          implements TrustAssociationInterceptor
          public myTAIImpl ()
          public boolean isTargetInterceptor (HttpServletRequest req)
               throws WebTrustAssociationException
               //return true if this is the target interceptor, else return false.
          public void validateEstablishedTrust (HttpServletRequest req)
               throws WebTrustAssociationFailedException
               //validate if the request is from the trusted proxy server.
               //throw exception if the request is not from the trusted server.
          public String getAuthenticatedUsername (HttpServletRequest req)
               throws WebTrustAssociationUserException
               //Get the user name from the request and if the user is 
               //entitled to the requested resource 
               //return the user. Otherwise, throw the exception
          public int init (Properties props)
               //initialize the implementation. If successful return 0, else reurn -1.
          public void cleanup ()
               //Cleanup code.

    If the init(Properties) method is implemented as described previously in your custom interceptor, this note does not apply to your implementation, and you can move on to the next step. Previous versions of include the public int init String(propsfile) method. This method is no longer required since the interceptor properties are not read from a file. The properties are now entered in the administrative console Custom Properties link of the interceptor using the administrative console or scripts. These properties then are made available to your implementation in the init(Properties) method. However, for backward compatibility, the init(String) method still is supported. The init(String) method is called by the default implementation of init(Properties) as shown in the following example.

    // Default implementation of init(Properties props) method. A Custom
       // implementation should override this.
       public int init (java.util.Properties props)
          String type = 
          String classfile=
          if (classfile != null && classfile.length() > 0 ) {
             return init(classfile);
          } else {
             return -1;

    Change your implementation to implement the init(Properties) method instead of relying on init String(propsfile) method. As shown in the previous example, this default implementation reads the properties to load the property file. The property gets the file containing the properties by concatenating .config to its value.

    The init(String) method still works if you want to use it instead of implementing the init(Properties) method. The only requirement is that the file name containing the custom trust association properties should now be entered using the Custom Properties link of the interceptor in the administrative console or by using scripts. You can enter the property using either of the following methods. The first method is used for backward compatibility with previous versions of WebSphere Application Server.

    Method 1... The same property names used in the previous release are used to obtain the file name. The file name is obtained by concatenating the .config to the property value. If the file name is called and is located in the C:/WebSphere/AppServer/properties directory, set the following properties...

    Method 2... Set the property in the trust association custom properties to the location of the file. For example, set the following property...

    Type the previous code as one continuous line.

    The location of the properties file is fully qualified (for example, C:/WebSphere/AppServer/properties/ Since the location can be different in a Network Deployment environment, use variables such as ${USER_INSTALL_ROOT} to refer to the WebSphere Application Server installation directory. For example, if the file name is called, and it is located in the C:/WebSphere/AppServer/properties directory, then set the following properties...

  3. Compile the implementation once you have implemented it. For example, $WAS_HOME/java/bin/javac -classpath $WAS_HOME/lib/wssec.jar;$WAS_HOME/lib/j2ee.jar

    1. Copy the class file to a location in the class path (preferably the $WAS_HOME/lib/ext directory).

    2. Restart all the servers.

  4. Delete the default WebSEAL interceptor in the administrative console and click New to add your custom interceptor.Verify that the class name is dot separated and appears in the class path.

  5. Click the Custom Properties link to add additional properties that are required to initialize the custom interceptor. These properties are passed to the init(Properties) method of your implementation when it extends the as described in the previous step.

  6. Save and synchronize (if applicable) the configuration.

  7. Restart the servers for the custom interceptor to take effect.

 Usage scenarioSecurity... Resources for Learning


See Also

Single Signon
Web component security