Resolving the portal user's log-in name with the user name on the Lotus Sametime server

The following setting is used for resolving name formats between two different types of user registries that use different schemas.

For example, if the user registry for IBM Lotus Sametime is native Domino Directory or Lotus Domino LDAP, and the user registry for WebSphere Portal is an LDAP directory such as Tivoli Directory Server, then setting the nameFormatForResolve value will load the STLinks applet with the distinguished name format used by the Lotus Sametime server.

Valid values include dn, loginName, and cn. A best practice is to use dn if it works in your environment, loginName if dn does not, and cn only if the others do not.

Guidelines for choosing a name format to use

The value should meet the following requirements:

• The value should be unique in the portal and in the Lotus Sametime user directory.

  For example, if either directory has multiple occurrences of the common name John Smith, do not use cn.

• The value should always be kept synchronized between the two user directories.

  For example, if you use the loginName jsmith in the portal directory, that name must be in the Lotus Sametime directory and used by the same person.

• The value must be included in an attribute that Lotus Sametime uses to search on when authenticating a user.

  For example, if Lotus Sametime uses a Lotus Domino LDAP directory, the search attribute should be included in the Search filter for resolving person names field of the LDAP document in the stconfig.nsf database. If Lotus Sametime uses a native (non-LDAP) Lotus Domino directory, the attribute should be in the Full Name or Short Name field of the Domino Directory database on the Lotus Sametime server.

1. Modify the CSEnvironment.properties file.

2. Modify the property: CS_SERVER_SAMETIME_1.nameFormatForResolve For example, CS_SERVER_SAMETIME_1.nameFormatForResolve=dn

Parent topic:

Collaborative Services environment properties

---