Ud Client Key Details

Note:

A thorough understanding of the LDAP protocol is required to understand the terminology and enter values on this page.

This GUI option is used to map keys from Sh requests to subscriber keys in the Ud server database when performing an LDAP search. The key value in Ud Attribute Name is prepended onto the value in the Base DN (when a filter is not defined) to form the search distinguished name (DN), which is used when searching for a subscriber in the LDAP database. If a search filter is required as well or instead of the Ud Attribute Name, this is defined in Filter and may also include a key token name in the string (such as "$(imsi)"). (When a value is defined in the Filter field, the Ud Attribute Name is not prepended onto the Base DN.)

One to three keys can be defined on this page. A minimum of one key must be configured to use the Ud client feature. Note that the order in which keys are defined on this page affects which key is used. When more than one key matches a subscriber during the LDAP search, the first matching key found in the order defined on this page is used. For example, this is used when re-subscribing for a subscriber. There is no triggering Sh request to initiate this, a check if performed periodically. A subscriber is read, the keys defined in the subscriber profile are checked with the configured key details, and the first matching defined key is used to initiate the re-subscribe request.