PQ72729: *WIN32* CANNOT USE CUSTOM SASL CLIENT FACTORY IN JNDI

APAR status

• Closed as program error.

Error description

• --
  A. DETAILS ABOUT THE PROBLEM
  JNDI does not load ClientFactory classes and fails with
  the exception: javax.naming.AuthenticationNotSupportedException.
  B. RECREATION STEPS
  1.Unzip the testcase SaslSimpleTest.zip
  2.compile SaslSimpleTest.java (javac SaslSimpleTest.java)
  3.run the testcase with command line arguments.
    java SaslSimpleTest bluepages.ibm.com
  C. JDK RELEASES (IBM/SUN) WHERE THE PROBLEM OCCURS / DOES NOT
  OCCUR
  Does not occur in SUN JDK 140 and 142
  Occurs in IBM JDK 140 and 1401
  
  -- PROBLEM ANALYSIS --
  LdapSasl.class is present in server.jar, but there is no
  ClientFactory.class in server.jar.
  When the application loads the LdapSasl.class, the
  bootclassloader finds LdapSasl.class
  and fails to locate ClientFactory.class and results in
  exceptions.
  -- PROBLEM RESOLUTION --
  LdapSasl.class and the ClientFactory.class should be picked up
  from the same jar file.
  Both are available in ldapsec.jar and hence removing the ldapsec
  related class files
  from server.jar file.
  -- TAGS --
  PMR: 25178,001,866
  CATEGORY: NA
  SUNBUG: NA
  -- EXTERNAL CONSIDERATIONS --
  Consider each of the following:
  External INTERFACE/BEHAVIOUR changes : no
  Class NAME changes : no
  PACKAGE changes : no
  SERIALIZATION issues : no
  PERSISTENT DATA changes : no
  NLS/TRANSLATION changes required : no
  README changes required : no
  PERFORMANCE impact : no
  Are any of the above affected (if YES, explain)? : no
  -- TESTING --
  What testing was performed and on what platforms?  Automated JCK
  and Regression tests
  AutoTest JCK testing completed (specify KEYWORD or PACKAGE): All
  Packages
  AutoTest regression testing completed (specify KEYWORD or
  PACKAGE): All Packages
  Is RawTC field completed? Yes
  -- MAINTENANCE --
  Have tracks been created on the following service releases (if
  NO, explain)?
      1401 yes
  Is the fix platform specific? No
  If YES, should it be ported to the following platforms
  (explain):
     AIX PPC32/PPC64
     Linux IA32/IA64/PPC32/390
     Win IA32/IA64
     zOS
  Is Link Status enabled (default), for auto creation of dev link
  defect (if NO, explain)? Yes
  <-AUTOAPAR OPEN TEMPLATE START->
  123456789-123456789-123456789-123456789-123456789-123456789-
  Using IBM JRE 1.4.0 with the JNDI LDAP JAR files
  (ldapsec.jar), JNDI does not load my ClientFactory classes
  and fails with the exception
  

Local fix

• With the command line option
  (given below)the problem is fixed.
  -Xbootclasspath/a:<JavaHome>\jre\lib\ext\ldapsec.jar
  

Problem summary

• JNDI does not load ClientFactory classes and
  fails with
  exception:javax.naming.AuthenticationNotSupportedException
  LdapSasl.class is present in server.jar, but there is no
  ClientFactory.class in server.jar. When the application
  loads the LdapSasl.class, the bootclassloader finds
  LdapSasl.class and fails to locate ClientFactory.class
  and results in exceptions.
  

Problem conclusion

• LdapSasl.class and the ClientFactory.class
  should be
  picked up from the same jar file. Both are available in
  ldapsec.jar and hence removing the ldapsec related
  class files from server.jar file.
  .
  To obtain the fix:
  Install build 20030410 or later
  

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

  JAVA(1.3/1.4 CO

• Fixed component ID

  5648C9800

Applicable component levels

• R140 PSN

     UP

• R14A PSN

     UP

• R14L PSN

     UP

• R14O PSN

     UP

• R14W PSN

     UP