Get the PDF

LDAP class-based configuration—<classConfig>

The attribute used to map to the login_id field must have memberExport="true". The User Sync Client uses the login_id as the primary key to map users and distribution lists. You must have memberExport="true" for the LDAP attribute that you intend to use as the login_id.

<classConfig>
: This node is used for mapping LDAP node types and

BlackBerry AtHoc

hierarchy node types. The LDAP data adapter produces one of the three node types: USER, TREE, and STATICLIST.

To view the sample output generated by the LDAP data adapter, see

samples/ldap/sample-output-LDAP-data-adapter.xml

in the User Sync Client installation folder.

The following example shows the structure of the <classConfig> node:

<!-- CLASS CONFIG
                 
To map the LDAP object of the given object class to a BlackBerry AtHoc entity, user, or tree; to define which LDAP attributes of a given object class are returned.
                 
 Attributes                                     
 objectClass   : LDAP object class
 type          : BlackBerry AtHoc entity type; could be "USER" or "TREE"
 nameAttribute : Specify the value of the LDAP attribute to
                 be used as the name in resulting hierarchy. 
-->
 
<classConfig>

  <class objectClass="user" type="USER">
    <attributes>
      <!--login_id-->
      <attribute memberExport="true">samaccountname</attribute>
      <!--last name-->
      <attribute>sn</attribute>
      <!--first name-->
      <attribute>givenname</attribute>
      <!--display name-->
      <attribute>displayname</attribute>
      <attribute>userAccountControl</attribute>
      <attribute multiValued="true">objectclass</attribute>
    </attributes>
  </class>
  <class objectClass="group" type="STATICLIST">
    <attributes>
      <attribute memberExport="true">cn</attribute>
      <attribute>name</attribute>
      <attribute>description</attribute>
    </attributes>
   </class>

  <class objectClass="*" type="TREE" />

</classConfig>

<class>
The <class> sub node under <classConfig> is used to map a specific objectClass in LDAP to one of the USER, STATICLIST, or TREE nodes in the output produced by the LDAP data adapter. To map a specific objectClass, set the value of the objectClass attribute to the object classes defined in LDAP. Specify the LDAP data adapter type in the type attribute. For example, <class objectClass="user" type="USER"> maps users in LDAP to the USER node in the LDAP data adapter output.

The <class> node has following sub node:

<attributes>
: This sub node is used to encapsulate the attributes that you want to fetch for that object class from LDAP. You can have multiple <attribute> sub nodes under the <attributes> node. Each <attribute> node specifies one LDAP attribute to fetch. The optional "multiValued" attribute specifies returning multiple values for this LDAP attribute. The optional "memberExport" attribute indicates that the current attribute should be exported as a static list member’s attribute.

The configuration code shown above directs the synchronization module to map LDAP users to user nodes and map all other LDAP entries to tree nodes.

This section also defines the custom LDAP attributes that need to be fetched and placed in the output XML of the LDAP data adapter.

Section:

Data adapter configuration