Using HCL Connections Photos for the Sametime Business Card

You can use the HCL Connections Profiles Photos for the Sametime Business Cards. One of the benefits of this method is the users are able to update their photos in Connections and automatically have them display the current photo in Sametime as well.

About this task

Calculating the Connections Profiles Photo URL

The Connections user photo can be retrieved from the /profiles/ API (REST: GET) which can process different key values from the parameter sent to uniquely identify the user details.

These parameters include:

<protocol>://<connections server>:<port>/profiles/

<protocol>://<connections server>:<port>/profiles/ email=

<protocol>://<connections server>:<port>/profiles/ uid=

<protocol>://<connections server>:<port>/profiles/ userid=

<protocol>://<connections server>:<port>/profiles/ key=

This configuration depends on which unique user identifier (userId) has been configured on the Sametime Community Server LDAP settings. To see this value, use the HCL Notes or Admin client to open the stconfig.nsf. In the LDAPServer document the field name is the “The attribute of the person entry that defines the internal ID of a Sametime user”, this is blank by default, which uses the distinguishedName attribute. If populated with another attribute, use this value instead. This value must be available to the Connections server as well.


In many cases the Sametime Community Server is configured to use the DN as the Sametime userId.

For example,the DN is: CN=Foo Bar,OU=Users,O=Example,C=US In this case the "distinguishedName" key should be used. The protocol is either http or https.

For example:

If the Connections server protocol is http and port is 9080, below is an example of the resulting URL after appending the user’s DN and encoding the spaces:

The Community server requires the absolute URL to be added to the person document or LDAP record as an attribute. Many LDAP servers (including Domino LDAP and Microsoft Active Directory) have an attribute that exists for this purpose called photoURL. Populate the full URL for the photo in the photoURL for each person record in the directory. For native Domino directories, the photoURL is located on the person document, miscellaneous tab.

LDAP Server Requirements

Some LDAP servers may not display the photoURL attribute to an anonymous bind (for example, Domino LDAP). Use an authenticated bind to the LDAP server when configuring LDAP services, or configure the LDAP server to render the photoURL to anonymous users.

URL accessibility

If the photo URL is a protected resource, Single Sign On (SSO) must be configured between Sametime Community and Connections servers. If the URL is available to anonymous users, SSO is not required.  When configuring SSO, the Connections server and Sametime server must share a common directory.

Related: Configuring SSO between Connections and Sametime

Configuring the Community Server userinfoconfig.xml file

If you have not already configured the userinfoconfig.xml file, review the applicable topic for your environment and complete the configuration before setting the photoURL.

  1. Update the <Details> section, copy and paste the below line. If your attribute name is not photoURL, change the FieldName value to the attribute containing the URL.

    <Detail Type="text/plain"Id="ImagePath"FieldName="photoURL"/>

    For the Sametime Proxy Server, add an additional <DetailType> for PhotoURL.

    For example:

    <Detail Type="text/plain"Id="PhotoURL"FieldName="photoURL"/>

  2. Update the Set params settings to include ImagePath and PhotoURL.
  3. Save and close the userinfoconfig.xml.
  4. It is a best practice to test the userinfoconfig.xml using a browser to ensure it displays correctly.
  5. If there are formatting errors, correct them before restarting the Community Server.
  6. Restart the Community Server for the change to take effect.