The new trust association interceptor (TAI) com.ibm.wsspi.security.tai.TrustAssociationInterceptor interface supports several new features and is different from the existing com.ibm.websphere.security.TrustAssociationInterceptor interface. The new TAI interface supports a multi-phase, negotiated authentication process. For example, some systems require a challenge response protocol back to the client. The two key methods in this new interface are:
The isTargetInterceptor method determines whether the request originated with the proxy server that is associated with the interceptor. The implementation code must examine the incoming request object and determine if the proxy server that forwards the request is a valid proxy server for this interceptor. The result of this method determines whether the interceptor processes the request.
A true value tells WebSphere Application Server to have the TAI handle the request.
A false value, tells WebSphere Application Server to ignore the TAI.
The negotiateValidateandEstablishTrust method determines whether to trust the proxy server from which the request originated. The implementation code must authenticate the proxy server. The authentication mechanism is proxy-server specific. For example, in the product implementation for the WebSEAL server, this method retrieves the basic authentication information from the HTTP header and validates the information against the user registry that WebSphere Application Server uses. If the credentials are not valid, the code creates the WebTrustAssociationException exception, which indicates that the proxy server is not trusted and the request is denied. If the credentials are valid, the code returns a TAIResult result, which indicates the status of the request processing with the client identity (Subject and principal name) to use for authorizing the Web resource.
The created TAIResults results have the following meanings:
TAIResult | Explanation |
---|---|
public static TAIResult create(int status); | * Indicates a status to WebSphere Application Server. The status cannot be SC_OK because the identity information is provided. |
public static TAIResult create(int status, String principal); | Indicates a status to WebSphere Application Server and provides the user ID or the unique ID for this user. WebSphere Application Server creates credentials by querying the user registry. |
public static TAIResult create(int status, String principal, Subject subject); | * Indicates a status to WebSphere Application Server, the user ID or the unique ID for the user, and a custom Subject. If the Subject contains a hashtable, the principal is ignored. The contents of the Subject become part of the eventual user Subject. |
Example
The following code sample indicates that additional negotiation is required:
// Modify the HttpServletResponse object
// The response code is meaningful only on the client
return TAIResult.create(HttpServletResponse.SC_CONTINUE);
The following code sample indicates that the TAI determined the user identity. WebSphere Application Server receives the user ID only and queries the user registry for additional information:
// modify the HttpServletResponse object
return TAIResult.create(HttpServletResponse.SC_OK, userid);
The following code sample indicates that the TAI determined the user identity. WebSphere Application Server receives the complete user information that is contained in the hashtable. For more information on the hashtable, see Configuring inbound identity mapping. In this code sample, the hashtable is placed in the public credential portion of the Subject:
// create Subject and place Hashtable in it
Subject subject = new Subject;
subject.getPublicCredentials().add(hashtable);
//the response code is meaningful only the client
return TAIResult.create(HttpServletResponse.SC_OK, "ignored", subject);
The following code sample indicates that an authentication failure occured. WebSphere Application Server fails the authentication request:
//log error message
// ....
throw new WebTrustAssociationFailedException("TAI failed for this reason");
The following methods are additional methods on the TrustAssociationInterceptor interface. These methods are used for initialization, shut down, and for identifying the TAI to WebSphere Application Server. For more information, see the Java documentation.
Related tasks
Configuring inbound identity mapping
Integrating third-party HTTP reserve proxy servers