PK91792: USER REGISTRY LOOKUPS BEING DONE REPEATEDLY EVEN BEFORE AUTHENTICATION CACHE TIMEOUT OCCURS

Fixes are available

APAR status

Closed as program error.

Error description

The initial login on the very first request is performed by
WebSphere by querying information from the current user
registry.

Subsequent requests being sent by the same client in the same
session should be authenticated via information from the
Authentication Cache, until the Authentication cache timeout or
LTPA token timeout has been reached.

However, under certain conditions WebSphere may continue to
query the current user registry to authenticate the client, even
if the Authentication cache timeout has not passed

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application Server
*                  V6.1.0                                      *
****************************************************************
* PROBLEM DESCRIPTION: AuthCache entries are not reused when   *
*                      SeedSecurityContext is used.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a RMI connection uses SeedSecurityContext which is used
by z/OS environment, a server which receives
SeedSecurityContext logs in the system by using credentials in
SeedSecurityContext. To do so, a hashtable login is performed.
The hashtable login doesn't lookup an entry of AuthCache
unless the hashtable contains a custom cache key. In this
case, hashtable doesn't contain a custom cache key.
However, once a login is completed, a created Subject is
inserted in AuthCache.
As a result, although the same SeedSecurityContext is sent
from a client to a server, the security code on the server
doesn't only reused the Subject which is in AuthCache, but
also add the same cache entry to AuthCache. Thus, multiple
cache entries which has the same security credentials are
stored in AuthCache.

Problem conclusion

With this fix, a custom cache key is generated based on
contents of SeedSecurityContext for reusing a cache entry.

APAR PK91792 is currently targeted for inclusion in Service
Level (Fix Pack) 6.1.0.33 of WebSphere Application Server V6.1.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK91792
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-07-20
Closed date
2010-03-12
Last modified date
2011-01-24

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

PM31096

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R610 PSY UK59848
UP10/09/11 P F009

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK91792: USER REGISTRY LOOKUPS BEING DONE REPEATEDLY EVEN BEFORE AUTHENTICATION CACHE TIMEOUT OCCURS

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

R610 PSY UK59848

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?