PH45689: LOGINMODULES CAN NO LONGER BE CREATED UNLESS THE LOGINMODULE CLASS IS IN THE CLASSPATH.

APAR status

• Closed as program error.

Error description

• PH37362 added an extra check for loginModule class to ensure the
  class is available. However it would break existing automation
  or scripts.
  
      java.lang.IllegalStateException:
  java.lang.IllegalStateException:
  java.lang.ClassNotFoundException:
  com.ibm.websphere.wssecurity.custom.MyTokenGenerateLoginModule
      at
  com.ibm.ws.security.admintask.securityDomain.ConfigureJAASLogin.
  afterStepsExecuted(ConfigureJAASLogin.java:1271)
              at
  com.ibm.websphere.management.cmdframework.provider.AbstractTaskC
  ommand.executeReal(AbstractTaskCommand.java:855)
              at
  com.ibm.websphere.management.cmdframework.provider.AbstractTaskC
  ommand.execute(AbstractTaskCommand.java:807)
      ...
      Caused by: java.lang.ClassNotFoundException:
  com.ibm.websphere.wssecurity.custom.MyTokenGenerateLoginModule
              at java.lang.Class.forNameImpl(Native Method)
              at java.lang.Class.forName(Class.java:339)
              at
  com.ibm.ws.security.admintask.securityDomain.ConfigureJAASLogin.
  getClassForName(ConfigureJAASLogin.java:1282)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  who configures loginModules                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: java.lang.ClassNotFoundException is     *
  *                      thrown if loginModule is not accessible *
  *                      at the time of loginModule              *
  *                      configuration                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  PH37362 added an extra check for loginModule class to ensure
  the
  class is available. If the class is not successfully loaded at
  the time of the loginModule configuration,
  ClassNotFoundException
  is thrown.
  This behavior would break existing automation or scripts if the
  loginModule configuration is performed prior to placing the
  loginModule classes.
  

Problem conclusion

• The code has been updated to not to require the loginModule clas
  to be loadable at the time of its configuration.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.22 and 9.0.5.12. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels