Defining the ID attribute for Active Directory for Sametime on IBM i

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.
  • Sametime policies are affected. Only the default policy is applied to the Sametime user.
Note that 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. Log in to the Integrated Solutions Console.
  2. Click Sametime System Console > Sametime Servers > Sametime Community Server.
  3. In the Sametime Community Servers list, click the deployment name of the Sametime Community Server.
  4. Click the Community Services tab.
  5. In the "LDAP Attributes" section of The attribute used for determining the internal user ID, enter the value DistinguishedName.
  6. Click OK.
  7. Restart the Sametime Community Server so the change can take effect.