Defining the ID attribute for Active Directory

If your Sametime® servers connect to an Active Directory (LDAP) server and you prefer to use the DN attribute rather than the objectGUID attribute for the Sametime internal user ID, you must assign the DistinguishedName attribute to be the internal ID for Sametime users. Doing so guarantees that Active Directory returns the DN attribute in the same case-sensitive and space-sensitive format. Forcing Sametime to use a consistent attribute for the internal user ID prevents awareness problems caused by ambiguous internal user IDs.

About this task

If you choose the DN attribute for the Sametime internal user ID, but do not assign the DistinguishedName attribute as the internal ID, you may see the following problems:

  • Awareness for some users does not work.
  • A user's name appears multiple times in the same Contact list.
  • Policies might not be applied, so the user might receive only default policies.
Note: You can assign the objectGUID attribute as the internal user ID to eliminate the need to run the name change tool in the future.

Procedure

  1. Launch the HCL Notes or Administration client, as the administrator.
  2. Click on Open > Applications > Open an application.
  3. In the servername field, enter the hostname of the Sametime server.
  4. In the filename field, enter “stconfig.nsf”.
  5. Scroll to the LDAPServer document and double-click to open it.
  6. Place the document in edit mode by double-clicking inside the document.
  7. In the field name “The attribute of the person entry that defines the internal ID of a Sametime user” enter “DistinguishedName”.
  8. Click File > Save to save the document.
  9. Restart the Community server for the change to take effect.