Set JVM custom properties, filtering HTTP requests, and enabling SPNEGO TAI in WAS (deprecated)

Performing this task helps you, as Web administrator, to ensure that WAS is configured to enable the operation of the Simple and Protected GSS-API Negotiation mechanism (SPNEGO) TAI with the required JVM property and with the appropriate filtering of HTTP requests. we need to know how to use the WAS admin console to manage the security configuration and have the proper authority to modify the security configuration of the appserver.

Deprecated feature:

In WAS V6.1, a TAI that uses the SPNEGO to securely negotiate and authenticate HTTP requests for secured resources was introduced. In WAS 7.0, this function is now deprecated. SPNEGO Web authentication has taken its place to provide dynamic reload of the SPNEGO filters and to enable fallback to the application login method. depfeat

Verify the configuration of the SPNEGO TAI. The deployment of the SPNEGO TAI can vary from a single WAS system on which a single application is running to a large multinode WAS ND (ND) cell, with dozens of appservers, hosting many applications. Every SPNEGO TAI is installed at the cell level. You must be aware of the particular SPNEGO TAI configuration.

The default behavior of the SPNEGO TAI is to not intercept HTTP requests. This default behavior ensures that the SPNEGO TAI can be installed into an existing cell, configured for a single appserver and not change any other appservers in the cell. Other WASs can run exactly as before within a given configuration. Decide whether or not to use the sample SPN<id>.filterClass and determine the exact filter properties to use.

The default behavior of the SPNEGO TAI is to use the<id>.filterClass and intercept all requests.

If the default behavior is not appropriate, we can use a customer provided class, or extend or modify the sample class as required. The system programmer interface, allows you to implement a custom filter to determine whether or not to intercept a particular HTTP request. With the default implementation, we can set filter rules for coarse as well as fine-grained criteria in selecting which HTTP requests to intercept.

For an alternative to the steps below for enabling the SPNEGO TAI, we can use scripting to perform the operation. See Enable the SPNEGO TAI as JVM custom property using scripting (deprecated) for the details.

Complete the following steps to enable the operation of the SPNEGO TAI with the selected filtering and with the JVM required property.


  1. Log on to WAS admin console.

  2. Click Servers > Application servers.

  3. Select the appropriate server. Under Server Infrastructure, expand Java and process management > Process Definition.

  4. Click Java virtual machine. Under Additional Properties, click Custom Properties. Create a new custom property, if required, by clicking New, then code in the name field and true in the value field.

  5. Click Apply > OK to save the configuration

  6. Identify when the SPNEGO TAI intercepts a given request. A set of filter properties is provided, but determine what is appropriate and modify the<id>.filterClass accordingly.



The appserver is configured and ready to provide a single sign-on environment for end users who have successfully authenticated in a Microsoft Active Directory domain. Restart each appserver configured for SPNEGO Web authentication. Then the SPNEGO TAI is set to filter HTTP request when it is operating.

Enable the SPNEGO TAI as JVM custom property using scripting (deprecated)
SPNEGO TAI JVM configuration custom properties (deprecated)


Related concepts

Single sign-on for HTTP requests using SPNEGO TAI (deprecated)


Related tasks

Set WAS and enabling the SPNEGO TAI (deprecated)
Set the client browser to use SPNEGO TAI (deprecated)
Create a single sign-on for HTTP requests using the SPNEGO TAI (deprecated)



SPNEGO TAI custom properties configuration (deprecated)