Configuring a custom string as the registration ID for authentication

Add a custom string as a registration ID 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 custom string for the SIP trunking telephone number, modify the configuration to use that string for authentication (skip this step if you are not using a custom string as the registration ID 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. If the Registration ID does not match any LDAP attribute, uncomment the following section of the authorization.xml file to allow registration to succeed. Note that only one 'non-strict' ID can be registered per user. Ensure that the following section of the authorization.xml file is not commented out:
    <!--<authorizationProperty>
    <description>non-strict authorization</description>
    <type>non-strict</type>
    </authorizationProperty>-->
  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.