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

Obtain the fix for this APAR.

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 WebSphere Application Server    *
  *                 V7.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 PM31096 is currently targeted for inclusion in Service
  Level (Fix Pack) 7.0.0.15 of WebSphere Application Server V7.0.
  
  Please refer to URL:
  //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack availability.
  

Temporary fix

Comments

APAR Information

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

  PK91792

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

Modules/Macros

• BBGUBINF BBOUBINF
  

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R700 PSY UK65061

     UP11/03/04 P F103

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.