PK75919: LTPA TOKEN TIMEOUT MAY NOT OCCUR PROMPTLY

Fixes are available

APAR status

Closed as program error.

Error description

While accessing WEB, login by using LTPAToken cookie may
result in extending LTPAToken expiration time longer than
LTPAToken timeout value.

There are two possible scenarios when this issue happens:

1) Security Attributes Propagation is enabled:
A propagation login occurs when LTPAToken is still valid if
a cushion time isn't considered, but expired if the cushion
time is considered. And then next login happened after
LTPAToken timeout, but AuthCache still has the entry.
For example, if LTPAToken timeout is 2 hours and cushion time
is 10 minutes. a propagation login happens between 1 hour
and 50 minutes to 2 hours after an initial login occured.
Then next propagation login happens before AuthCache entry
is evicted. Normally, it'll happen when the next login
happens within 15 minutes after previous propagation
login.

2) Security Attributes Propagation is disabled:
This issue may happen if a propagation login happens after
AuthCache entry was evicted. And next propagation login
has made by AuthCache entry.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
****************************************************************
* PROBLEM DESCRIPTION: While accessing WEB, login by using     *
*                      LTPAToken cookie may result in          *
*                      extending LTPAToken expiration time.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a Subject object is constructed by using LTPAToken
cookie, the Subject expiration doesn't set the remaining
timeout value which can be computed by a value in LTPAToken
cookie. Then, the constructed Subject is stored into AuthCache
by using the original LTPAToken cookie as a cache key.

After that, newly constructed Subject is returned when cache
lookup is done by the original LTPAToken cookie.
Since token expiration check is done against the expiration
time of Subject which was returned from AuthCache, token
timeout won't occur at the time of the expiration of LTPAToken
cookie.

Problem conclusion

With this code fix, the expiration check is done by using the
value of LTPAToken cookie which has the original expiration
time.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.1.0.23 and 7.0.0.5.  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
PK75919
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-19
Closed date
2009-01-12
Last modified date
2009-01-12

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
R61P 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

PK75919: LTPA TOKEN TIMEOUT MAY NOT OCCUR PROMPTLY

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

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?