PM47513: SPNEGO TAI WITH MULTIPLE SPNS "FILTER" PROPERTIES CONFIGURED ONLY USES LAST SPN DEFINED.

Fixes are available

APAR status

Closed as program error.

Error description

If a SPNEGO filter with properties configured such as:

com.ibm.ws.security.spnego.SPN1.hostName -> server1.ibm.net
com.ibm.ws.security.spnego.SPN1.filter ->
request-url"caret"=criteria-1
com.ibm.ws.security.spnego.SPN2.hostName -> server2.ibm.net
com.ibm.ws.security.spnego.SPN2.filter
-> request-url"caret"=criteria-2

Then when the TAI is called on requests for URL on
server1.ibm.net - the filter defined (request contains
"criteria-1") is not used, but instead the last
filter (request contains "criteria-2") is used.

Local fix

The only work around available is to make
com.ibm.ws.security.spnego.SPN2.filter
 -> request-url"^"=criteria-2 | criteria-1

Only by making the "last" filter contain all the required
conditions will the interception criteria be properly applied.
However, if there are contradicting criteria, there is
no way to support multiple SPNs in the same Application
Server cell.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: SPNEGO TAI with multiple SPNs           *
*                      "filter" properties configured only     *
*                      uses the last SPN defined in a server.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The error is caused by a fault in the
com.ibm.ws.security.spnego.HTTPHeaderFilter class.
The Vector containing the filterCondition should not be a
static member.

Problem conclusion

With this fix, HeaderFilter clas has been changed to make
the filterCondition Vector non-static.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.21 and 8.0.0.2.  Please refer to the Recommended
Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM47513
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-09
Closed date
2011-09-26
Last modified date
2011-09-26

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM47513: SPNEGO TAI WITH MULTIPLE SPNS "FILTER" PROPERTIES CONFIGURED ONLY USES LAST SPN DEFINED.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?