JR52835: Cannot log on when user exists on LDAP but not on the WebSphere Commerce database.

APAR status

• Closed as program error.

Error description

• When a user attempts to log on by using LDAP, if the user exists
  on LDAP but not on the database, WebSphere Commerce tries to
  create the user in the database. there are multiple attempts to
  create the user on the database.
  
  UserSyncBean.findByLogonId() creates the parent organization of
  the user in the WebSphere Commerce database, since that
  organization only exists in LDAP at the beginning. Later, when
  LDAPAuthenticationCmd calls UserSyncBean.findByLogonId() again,
  UserSyncBean.findByLogonId() tries to recreate the parent
  organization (using a different memberID), because it is looking
   up the organization based on DN, and not by OrgEntityName. This
   is where an exception is thrown and the transaction is rolled
  back.
  
  There is a limitation of EJBs that you can only find a newly
  created EJB/databaseEntry if you find it using the attributes
  that were passed in the original ejbCreate() method.
  

Local fix

Problem summary

• USERS AFFECTED:
  Users on WebSphere Commerce v7 that is configured with LDAP.
  
  PROBLEM ABSTRACT:
  Cannot log on when user exists on LDAP but not on the WebSphere
  Commerce database.
  
  BUSINESS IMPACT:
  Shoppers whose registration data exists on LDAP but not on the
  WebSphere Commerce database cannot log on.
  
  RECOMMENDATION:
  

Problem conclusion

• To solve the issue, add ServerJDBCHelperAccessBean.flush() to
  SyncBeanBase.create()
  

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

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R700 PSY

     UP