Configuring business cards using an LDAP directory
Follow these steps to configure the business card using an LDAP directory. Domino® LDAP is considered an LDAP directory.
Before you begin
- IBM® Domino and IBM Sametime® Community Server have been installed and configured
- Sametime authentication is configured to use an LDAP directory
- The LDAP server is running and accessible by the Sametime Community Server
- All LDAP attributes needed by Business Card are accessible for query via anonymous connection or by using a specific bind account and password
- The Sametime Community Server is running
- For Domino LDAP only: To allow anonymous users to access required user details, you can edit the All Servers document in names.nsf. Under the LDAP tab, all LDAP attributes that you want to be retrieved by anonymous users should be added to the list of Anonymous Users Can Query.
- Photos must be less than 45 KB (recommended: 10 KB) and must be in the .jpg or .gif file type
About this task
Procedure
What to do next
Special considerations
In a configuration where:- Sametime is configured with an LDAP directory
- UserInfo is configured to ignore configuration updates
- The Sametime ID is configured to an attribute different than a DN
- Open the UserInfoConfig.xml file.
- Locate the StorageDetail tag of the relevant
LDAP directory and add the following flags:
UserIdAttribute= attribute_name PersonObjectClass= object_class_name
- Save and close the file.
- Restart the server.
The UserInformation service initially loads the configuration from UserInfoConfig.xml and then receives configuration updates from the Sametime System Console. However, the Sametime System Console cannot be modified on the fly to contain additional attributes. So additional user attributes you define for a business card would not be included in the configuration updates from the Sametime System Console. In this case, all business card configuration should be done in UserInfoConfig.xml, and configuration updates from the Sametime System Console should be disabled using these steps:
- Open the UserInfoConfig.xml file.
- Locate the UserInformation tag of the relevant
LDAP directory and add the following flag:
<ReadStConfigUpdates value="false"/>
- Save and close the file.
- Restart the server.
An optional setting in UserInfoConfig.xml file lets you map a detail to more than one attribute. As a result, the returned value for a detail is composed of a list of attributes retrieved from the storage.
You can do this by mapping an item to a comma-separated list of attributes.
<Detail Id="Telephone" FieldName="telephoneNumber,mobile" Type="text/plain" />
The response can contain a list of values separated by any character chosen by the administrator. To apply the new separator, edit the UserInfoConfig.xml file.
- Open UserInfoConfig.xml in an editor.
- Choose the Detail tag that you want to use to retrieve a list of attributes.
- Complete the FieldName property with the list of attributes to retrieve, separated by commas.
- Add an additional property: DisplaySeparator.
Set its value to the required character that should appear in the
response XML between any 2 retrieved attributes values. For example, <Detail
Id="Telephone" FieldName="telephoneNumber,mobile" Type="text/plain"
DisplaySeparator=" / "/>.Note: To ensure a correct display on iOS, use the
/
symbol with a space before and after as thedisplaySeparator
. - Log in to the WebSphere Integrated Solutions Console as the WebSphere administrator.
- Click .
- In the Sametime Community Servers list, click the deployment name of the server with the connectivity information that you want to change.
- Click the Business Card tab.
- Verify that the mapping of this detail (the Telephone detail in the example) is empty.
- Click OK.
- Restart the server.