PI27898: JAASLOGINCONTEXTENTRIES WITH SAME NAME CAUSES WRONG BEHAVIOR.

8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• See defect 148890
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: The duplicate name of                   *
  *                      JaasLoginContextEntries might cause     *
  *                      unexpected behavior.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When specifying the id for a jaasLoginContextRef as follows:
  ---------------------
  <contextService jndiName="concurrent/securityContextSvc">
  <securityContext deserializeLoginContextRef="testMyOwnId"/>
  </contextService>
  <jaasLoginContextEntry id="testMyOwnId" name="testMyOwnName"
  loginModuleRef="hashtable,userNameAndPassword,certificate,token"
  />
  <jaasLoginContextEntry id="testMyOwnId2" name="testMyOwnName"
  loginModuleRef="hashtable,userNameAndPassword,certificate,token"
  />
  --------------------
  the runtime code will incorrectly use the second entry with id
  "tedtMyOwnId2" because these two entries have the same name. The
  current implementaion resolves the jaasLoginContextEntry which
  is specified by deserializeLoginContextRef with the name
  attribute instead of the id attribute.
  

Problem conclusion

• In order to maintain the backword compatiblity, the current
  behavior is unchanged. However, CWWKS1122W message is logged
  when this condition is detected for administrators to notify
  that there are duplicate entries.
  
  The fix for this APAR is
  currently targeted for inclusion in fix pack 8.5.5.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 is sysrouted FROM one or more of the following:

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

Fix information

• Fixed component name

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP