PI48220: The hashtable login module does not honor the uniqueId and secur ity name when passing then userId

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

• After user kerberized their application Servers running on
  Liberty Profile, their Login Module (which basically only
  sets
  the username to lowercase  and removes the LDAP formating),
  does not work anymore. (SRLoginModule.jar).
  
  
   
  

Local fix

• No work around at this time.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile who configure a      *
  *                  Kerberos loginModule                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a Kerberos LoginModule is added to *
  *                      existing login configuration,  the user *
  *                      asserted by the Custom Login Module is  *
  *                      not honored.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a Kerberos loginModule is added to the existing login
  Module configuration,  the user that is asserted by the custom
  Login Module is no longer honored.
  

Problem conclusion

• The code is updated to honor the user asserted by the custom
  login module.
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.8.  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