PM26317: CONCURRENT LOGONS SOMETIMES CAUSE INCORRECT AUTHCACHE DATA

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Sometimes an LTPA token is passed along that has expired.
  
  [10/25/10 10:39:05:745 EDT] 0000240b AuthCache < getSubject Exit
  Subject:
  Principal: xxxxxxxxx.xxxxxxx.xxxxxxxxxx.com:389/cp33395
  Public Credential:
  com.ibm.ws.security.auth.WSCredentialImpl@6f626f62
  Private Credential:
  com.ibm.ws.security.token.SingleSignonTokenImpl@6cd06cd0
  Private Credential:
  com.ibm.ws.security.token.AuthenticationTokenImpl@325a325a
  Private Credential:
  com.ibm.ws.security.token.AuthorizationTokenImpl@466e466e
  [10/25/10 10:39:05:745 EDT] 0000240b LTPAToken2    3
  Expiration returned from expire field in token: Mon Oct 25
  10:50:01 EDT 2010
  [10/25/10 10:39:05:745 EDT] 0000240b ContextManage <
  isTokenMatch: true
  Exit
  
  Although returned Subject is completely different from the
  original one, isTokenMatch method, which checks whether
  LTPAToken cookie and token byte in LTPAtoken are identical,
  returns they are identical.  Thus, no expiration date check
  by using LTPAToken cookie is performed.  Later, LTPAToken
  cookie is extracted from this Subject which has expired
  LTPAToken cookie.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Incorrect Subject will be generated     *
  *                      under concurrent logins by the same     *
  *                      user id.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  There are several locations that a Subject object is
  constructed by using information in LTPAToken cookie. During
  processing this scenario, LTPAToken itself is set as a part of
  newly created Subject. However, there is a possibility that
  LTPAToken cookie itself is expired. As a result, when there is
  a situation that the code validates expiration time by using
  LTPAToken cookie, it returns incorrect expiration time.
  Another issue in this scenario is that an expired Subject in
  AuthCache might be reused during creating a new Subject
  during processing a hashmap login, or login by using a custom
  cache key.
  

Problem conclusion

• With this fix, the way to accessing AuthCache is modified to
  avoid generating incorrect Subject.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 6.1.0.37 and 7.0.0.17.  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 is sysrouted FROM one or more of the following:

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

  PM35357

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