JR53607: USER SYNCHRONIZATION CREATES NEW USERS FOR EXISTING USER NAMES THAT CONTAIN TRAILING BLANKS (WHITE SPACES)

8.5.6.0-WS-BPM-IFJR53607
bpm.8560.cf1.delta.repository.1
bpm.8560.cf1.delta.repository.2
Version 8.5 Refresh Pack 7 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• When trailing blanks are removed from a user name in LDAP for a
  user that has already been synchronized with IBM Business
  Process Manager (BPM), this user is considered a new user during
  user synchronization, creating a duplicate entry in the
  database. Because strings that have and do not have trailing
  white spaces are considered to be equivalent for most comparison
  operations on the database, a query for a specific user name
  returns a list of users with a given name (and, optionally,
  white spaces) instead of a single user. As a result, tasks
  might be assigned to the wrong user ID.
  

Local fix

Problem summary

• No additional information is available.
  

Problem conclusion

• A fix is available for IBM BPM V.8.5.6.0 that prevents users
  from being created that were corrected in LDAP from a name that
  contains one or more trailing white spaces to the same name
  without the white spaces. In general, it is strongly discouraged
  to change user names in LDAP if these have already been
  synchronized to IBM BPM.
  
  In addition, you can use the configuration property in the fix
  to specify whether the information of a user already in the
  database should be updated with the information of a user with
  the name that was corrected in LDAP. This property is set to
  true by default. If the property remains set to true,
  information for the user already in the database is updated when
  you specify the corrected user name and select Synchronize in
  the Process Admin Console or log in with the user ID. Selecting
  Existing User Synchronize does not update the user's
  information.
  
  If you set this property to false, the user is not recognized as
  equivalent to the corrected user in LDAP. As a result, user
  information including the full name and provider name are set to
  null. You can set this property to false in the 100Custom.xml
  file:
  
  <common merge="mergeChildren">
    <security merge="mergeChildren">
      <update-user-ignoring-trailing-blanks merge="replace">false
      </update-user-ignoring-trailing-blanks>
    </security>
  </common>
  
  On Fix Central (http://www.ibm.com/support/fixcentral), search
  for JR53607:
  
  1. Select IBM Business Process Manager with your edition from
    the product selector, the installed version to the fix pack
    level, and your platform, and then click Continue.
  
  2. Select APAR or SPR, enter JR53607, and click Continue.
  
  When you download fix packages, ensure that you also download
  the readme file for each fix. Review each readme file for
  additional installation instructions and information about the
  fix.
  

Temporary fix

• Not applicable
  

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

  BPM STANDARD

• Fixed component ID

  5725C9500

Applicable component levels