PK93018: Custom JAAS Subject Data absent when request is driven within LTPA cushion window

Fixes are available

APAR status

Closed as program error.

Error description

When users of WebSphere Application Server's Trust Association
Interceptor (TAI) functionality drive requests that have
previously been authenticated via LTPA (ie, requests that
already contain an LTPA cookie), custom JAAS subject data that
may have been added on the initial login could be erroneously
absent if the request is driven within the LTPA cushion window.
WebSphere Application Server fails to invoke the TAI in this
scenario.

The LTPA cushion window is a 10 minute fixed time window whereby
if a request is driven, and the credential has less than 10
minutes until it will expire, WebSphere Application Server will
make an attempt to refresh the credential primarily to help
minimize latency if the request is intended for an external
downstream server.

Local fix

-
Search Keywords: missing omit security custom

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server's Trust Association Interceptor      *
*                  (TAI) functionality                         *
****************************************************************
* PROBLEM DESCRIPTION: Custom JAAS subject data was not        *
*                      being refreshed correctly when          *
*                      requests were driven that fell within   *
*                      the LTPA token cushion window.          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebSphere Application Server was not properly invoking the
custom TAI code when within the cushion window. New subjects
did not contain the custom JAAS subject data.

Problem conclusion

WebSphere Application Server has been modified to properly
invoke the TAI when within the cushion window. To take
advantage of this functionality, a security custom property
must be set.

In the Integrated Solutions Console, click Security > Secure
administration, applications, and infrastructure > Custom
properties. You can click New to add a new custom property and
its associated value.

Property: com.ibm.ws.security.failSSODuringCushion
Value: true

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

Temporary fix

ZE Fix Error, see PM30025 and PM30969 2011/03/07

Comments

APAR Information

APAR number
PK93018
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-03
Closed date
2009-10-14
Last modified date
2011-03-07

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK93018: Custom JAAS Subject Data absent when request is driven within LTPA cushion window

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

R61A PSY

R61H PSY

R61I PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?