PI56559: CHANGE IN THE ODER OF LOGIN MODULES IN SECURITY.XML AFTER RUNNING THE MIGRATION SCRIPTS.

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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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

• Running the migration scripts from 7.0.0.19 to 8.5.5.8 - the
  scripts change the order of login modules in security.xml
  

Local fix

• To change the order of login modules.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server performing a migration with Kerberos *
  *                  login modules configured.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unable to authenticate to               *
  *                      administrataive console via Kerberos    *
  *                      after migration                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  After migrating a server to V8.0 or V8.5, logging into the
  administrative console fails even with correct credentials.
  Trace will show the following error:
  login failed:
  com.ibm.websphere.security.auth.WSLoginFailedException:
  WSPrincipal is null in commit (phase 2) stage.
  This occurs because the ltpaLoginModule is moved in front of
  the WSKrb5LoginModule in security.xml by the migration
  process, and the commit is being done on LTPA before Kerberos,
  removing WSPrinciple.
  

Problem conclusion

• Migration code was adjusted to perform the requisite
  rearranging of login modules for all versions of security.xml,
  as it was only doing so at the server level before. Therefore,
  the Kerberos login module will be first, and
  authentication will not fail with correct credentials.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 8.5.5.10 and 8.0.0.13.  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

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY

     UP

• R850 PSY

     UP