Configuring a custom LDAP attribute for authentication

Add a custom attribute to the LDAP directory's login property so it can be used for authenticating users who log in to IBM® Sametime® clients.

About this task

By default, the SIP Proxy/Registrar is configured to use the mail attribute for authentication. If you are using a different attribute for the SIP trunking telephone number, modify the configuration to use that attribute for authentication (skip this step if you are not using a custom attribute for authentication).

Procedure

  1. On the computer hosting the deployment manager of SIP Proxy/Registrar, navigate to the server's directory:
    DM_install_root/config/cells/Cell_name/nodes/Node_name/servers/Server_name
    Note: If the SIP Proxy/Registrar is clustered, use the cluster's deployment manager profile.
  2. Open the authorization.xml file in a text editor, locate the authorizationProperty section, and add the repositoryAttr attribute to specify the LDAP attribute that will contain the telephone number used by SIP-based calling:
    <authorizationProperty>
      <description>Telephone number for SIP trunking</description>
      <type>telephoneNumber</type>
      <!-- VMM property name-->
      <repositoryAttr>LDAP_attribute< /repositoryAttr> 
</authorizationProperty>

    Where LDAP_attribute is the name of the LDAP attribute that contains the telephone number.

  3. Save and close the file.
  4. If you are working with a cluster of SIP Proxy/Registrars, make this change to every instance of this file on the deployment manager's server (you can copy the modified file to the additional profiles).
  5. Restart the server or cluster:
    • For a stand-alone Media Manager or SIP Proxy/Registrar, restart it now as follows:
      1. In the server's Integrated Solutions Console, click Servers > Server Types > server_type.
      2. In the list of servers, select your server and click the Restart button at the beginning of the table.
      3. Click the Refresh button and verify that all components are active.
    • For a cluster of SIP Proxy/Registrars, synchronize and then restart the cluster:
      1. In the deployment manager's Integrated Solutions Console, click System Administration > Nodes.
      2. Select all nodes in the cluster, and then click the Full Resynchronize button at the beginning of the table.
      3. Back in the navigation tree, click Servers > Clusters > WebSphere application server clusters.
      4. In the clusters, table, select the SIP Proxy/Registrar cluster, and then click the Stop button at the beginning of the table.
      5. Wait for the cluster to stop.
      6. Now click the Start button at the beginning of the table.

What to do next

Proceed to Creating and editing routing rules for SIP-based calls.