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

Before you start setting up your business cards, be sure the following conditions are true for your site.
  • 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

This task must be completed separately for each server within a Sametime Community Server cluster.

Procedure

  1. Log in to the WebSphere® Integrated Solutions Console as the WebSphere administrator.
  2. Click Sametime System Console > Sametime Servers > Sametime Community Servers.
  3. In the Sametime Community Servers list, click the deployment name of the server with the business card information that you want to add or change.
  4. Click the Business Card tab.
  5. In the Business Card Contents section, select the attribute you want displayed in users' business cards, and then click Add to include the selected attribute. If you do not want to display any pre-selected information, select each attribute, and then click Remove.
  6. Under Attribute Definition, choose Attribute Values that are appropriate for your deployment. Each LDAP directory has its own naming schema, so be sure to confirm that each attribute value selected for display is mapped to the correct LDAP attribute as defined by your LDAP schema. If you prefer to map another attribute value to the attribute name instead of the default value, then choose User Defined.
    The following table lists the default attribute value that is mapped to each attribute name.
    Table 1. Attribute names and values
    Attribute Name Attribute Value
    E-mail address mail
    Telephone telephoneNumber
    Title title
    Photo jpegPhoto

    (requires the inetOrgPerson objectClass)
    Address postalAddress
    Company ou
    Name cn

    Domino LDAP does not contain the postalAddress field. The value retrieved for this LDAP attribute is the concatenation of City, State/Province, and Country. Also, Domino LDAP contains a hidden field for the ou attribute. This field cannot be set through the Domino LDAP, and a third-party LDAP management tool can be used to add a value to it.

  7. If you select User Defined for an Attribute Value, then enter an attribute to map to the Attribute Name.
  8. Click OK.
  9. Restart the Sametime Community Server.

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
You must add additional parameters to the UserInfoConfig.xml file to correctly support this type of Sametime ID.
  1. Open the UserInfoConfig.xml file.
  2. Locate the StorageDetail tag of the relevant LDAP directory and add the following flags: 
    UserIdAttribute= attribute_name
PersonObjectClass= object_class_name
  3. Save and close the file.
  4. 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:

  1. Open the UserInfoConfig.xml file.
  2. Locate the UserInformation tag of the relevant LDAP directory and add the following flag:
    <ReadStConfigUpdates value="false"/>
  3. Save and close the file.
  4. 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.

  1. Open UserInfoConfig.xml in an editor.
  2. Choose the Detail tag that you want to use to retrieve a list of attributes.
  3. Complete the FieldName property with the list of attributes to retrieve, separated by commas.
  4. 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 the displaySeparator.
  5. Log in to the WebSphere Integrated Solutions Console as the WebSphere administrator.
  6. Click Sametime System Console > Sametime Servers > Sametime Community Servers.
  7. In the Sametime Community Servers list, click the deployment name of the server with the connectivity information that you want to change.
  8. Click the Business Card tab.
  9. Verify that the mapping of this detail (the Telephone detail in the example) is empty.
  10. Click OK.
  11. Restart the server.