Preparing user IDs for RESOLVE mode

Before you use the name conversion utility in RESOLVE mode, you must make LDAP directory changes (if needed) and IBM® Sametime® configuration changes.

About this task

If your LDAP directory does not contain an attribute with a unique value in the person entry, then you must change to the schema to provide one. See the documentation provided by your specific LDAP vendor. See also RFC 4530 (http://www.ietf.org/rfc/rfc4530.txt) which introduces the entryUUID attribute in LDAP directories. The value of this attribute is constant by definition, which makes it suitable for the user ID mapping in Sametime. If your LDAP directory does not support this attribute, consider extending the directory schema to support it. If you prefer to use an existing attribute instead of modifying the schema, choose an attribute that is not likely to change when users change their name or relocate. Here are examples of stable attributes in some well-known LDAP servers:
  • IBM Directory Server: ibm-entryUUID
  • Domino® LDAP: dominounid
  • Novell Directory Server (NDS): guid
  • SunOne: nsuniqueid
  • Active Directory: objectGUID

Unlike the ID name conversion mode, which expects a table of oldName and newName entries as input, the RESOLVE mode does not expect any input from the administrator. When the name conversion is run in this mode, it looks up each user ID in the database against the directory, and replaces the old user ID with the directory user ID. The tool accomplishes this by using the StResolve service to look up each person. This requires the administrator to make the LDAP configuration change to use the new user ID mapping before running the tool on every Sametime server in the organization.