PI22900: IMPORTING USERS FROM LDAP USING WILDCARD FAILS

IBM UrbanCode Deploy Fix Pack 2 (6.1.0.2) for 6.1
IBM UrbanCode Deploy Interim Fix 1 for 6.1.0.2
IBM UrbanCode Deploy Fix Pack 3 (6.1.0.3) for 6.1
IBM UrbanCode Deploy Fix Pack 4 (6.1.0.4) for 6.1

APAR status

• Closed as program error.

Error description

• 1. Importing users from LDAP, using * to match multiple
  characters, creates userids which contain * instead of the
  matched characters.
  
  However the name and the email are imported correctly.
  
  For example, if you attempt to import all users that contain the
  string "Tom", using: *Tom*, then, if at least a matching user
  exists, it will be imported as:
  
  userid= *Tom*
  name = Tom Smith
  e-mail = tom.smith@example.com
  
  
  2. If multiple userids should be imported because they match the
  expression containing the wildcards, then only one is actually
  imported.
  
  3. The problem is not restricted to the use of wildcards. For
  example, assume that you configured the following user filter:
  (&(|(mail={0})(cn={0}))(objectclass=ePerson))
  so that you can search by user name (cn) or by e-mail address
  (mail).
  
  Whatever you search for, if a match is found will be used as the
  userid in UrbanCode Deploy.
  
  This leads to inconsistent results, as some userids will be
  e-mails and some will be names.
  
  It would be helpful if the userid in UrbanCode Deploy was taken
  always from the same field in LDAP, for example the uid, or a
  specific field that the user designates.
  

Local fix

• Import users from LDAP specifying the string that you want to
  use as userid in UrbanCode Deploy.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Any                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * 1. Importing users from LDAP, using * to match multiple      *
  * characters, creates userids which contain * instead of the   *
  * matched characters.                                          *
  *                                                              *
  * However the name and the email are imported correctly.       *
  *                                                              *
  * For example, if you attempt to import all users that contain *
  * the                                                          *
  * string "Tom", using: *Tom*, then, if at least a matching     *
  * user                                                         *
  * exists, it will be imported as:                              *
  *                                                              *
  * userid= *Tom*                                                *
  * name = Tom Smith                                             *
  * e-mail = tom.smith@example.com                               *
  *                                                              *
  *                                                              *
  * 2. If multiple userids should be imported because they match *
  * the                                                          *
  * expression containing the wildcards, then only one is        *
  * actually                                                     *
  * imported.                                                    *
  *                                                              *
  * 3. The problem is not restricted to the use of wildcards.    *
  * For                                                          *
  * example, assume that you configured the following user       *
  * filter:                                                      *
  * (&(|(mail={0})(cn={0}))(objectclass=ePerson))                *
  * so that you can search by user name (cn) or by e-mail        *
  * address                                                      *
  * (mail).                                                      *
  *                                                              *
  * Whatever you search for, if a match is found will be used as *
  * the                                                          *
  * userid in UrbanCode Deploy.                                  *
  *                                                              *
  * This leads to inconsistent results, as some userids will be  *
  * e-mails and some will be names.                              *
  *                                                              *
  * It would be helpful if the userid in UrbanCode Deploy was    *
  * taken                                                        *
  * always from the same field in LDAP, for example the uid, or  *
  * a                                                            *
  * specific field that the user designates.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fixed in IBM UrbanCode Deploy 6.1.0.2
  

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

  UC DEPLOY

• Fixed component ID

  5725M5400

Applicable component levels

• R600 PSN

     UP

• R600 PSY

     UP

• R601 PSN

     UP

• R601 PSY

     UP

• R610 PSN

     UP

• R610 PSY

     UP