Adding an AD/LDAP synchronizer is a two-step process: configure Connection Settings, and then configure Field Mappings.
To help you generate the LDAP path, which is a required field under Connections, use the LDAP Path Assistant.
The LDAP Path Assistant can make it easier to formulate the LDAP URL for a synchronizer, provided that the synchronizer is connecting to an Active Directory server. The Assistant may not work with other kinds of LDAP servers.
To use the assistant, enter the fully qualified domain name (FQDN) of the domain controller in the Assistant. The Assistant will then create an LDAP URL with the format ldap://<domain-controller-name>/<DC= separated top level domain controller name components>
NOTE: The path assistant is only intended to assist you in the creation of LDAP URL. Path assistant may not always work depending on how your LDAP server is configured.
For example:
Click here to see additional information about the Search context field.
The Search context is an LDAP path relative to the absolute path specified in the LDAP path field. Together, the values you configure for the LDAP path and Search context fields determine which LDAP object is the starting point for the search query. For example, if you use the following hierarchy in your LDAP database:
XYZ Company
-> New York Branch
-> Sales Department
-> US Sales
-> Eastern US
and you want to synchronize all accounts from the Eastern US Organizational Unit, you would specify the LDAP fields as follows:
If your search should begin at the root object (for example, the XYZ Company object), you can leave the Search context blank.
Configure the AD/LDAP Connection Settings.
Connection Settings: Allow MiCollab Client to connect to the AD/LDAP directory and import information. Add or edit the following Connection Settings:
NOTE: The LDAP Path Assistant is only intended to assist you in the creation of the LDAP URL. Depending on how your LDAP server is configured, it may not always work.
NOTE: The specified user must have privileges to read information relevant to all accounts that expect to be synced into MiCollab Client.
NOTE: The Default Feature Profile does not include any features. To assign features to users when you create accounts during the initial synchronization, you must first create a Feature Profile that includes the features you want to use, and then you can select it here. Refer to the Licensed Features and Synchronization topic before selecting a Feature Profile.
Timestamp: MiCollab Client Service uses the modification timestamp on LDAP objects to optimize processing. This is mainly used for display picture importing and MiCollab Client tries to import only those display pictures which have changed on the LDAP server since the last time MiCollab Client did a successful sync.
Timestamp attribute: This is the attribute name of the LDAP field which contains the modification timestamp. In case of Active Directory, the attribute is whenChanged. If your LDAP server has some other attribute name, specify that instead.
NOTE: If this attribute is left blank, MiCollab Client Service will try to import display pictures for all eligible accounts, regardless of when they were modified. While a blank timestamp attribute is not a recommended configuration for regular use (because display picture import can consume substantial cpu/ memory), it can be used to force a re-import of all display pictures if required for troubleshooting, error recovery, etc. To do this, blank out the timestamp attribute and perform a sync. After the sync, set the timestamp attribute back to its original value and sync again.
Timestamp syntax: The format of the timestamp value contained in the timestamp attribute. For Active Directory, this is X680 format. Some older LDAP servers may use the X208 format.
Do one of the following:
Configure the Field Mappings between the directory and the MiCollab Client accounts.
Field Mappings specify how AD/LDAP database fields are mapped to MiCollab Client account fields when the information is synchronized.
Field |
Default Value |
Description |
Directory key |
objectGUID |
This is the unique key that identifies the account in the directory. If the directory object does not have a value for this field, it is not imported. |
PBX node |
facsimileTelephoneNumber |
Identifies the PBX node, or switch, that the user’s phone is configured on. If the directory object does not have a value for this field, it is not imported. |
First name |
givenName |
The user’s first name. This field can be blank. |
Middle name |
initials |
The user’s middle name. This field can be blank. |
Last name |
sn |
The user’s last name. This field can be blank. |
Login ID |
sAMAccountName |
The login ID that the MiCollab Client Desktop Client uses to authenticate with the MiCollab Client Service. This field can be blank. |
Desk phone extension |
ipPhone |
The user’s desk phone extension. This field can be blank. |
Soft phone extension |
otherIpPhone |
The user’s soft phone extension. This field can be blank. |
Company name |
company |
The user’s company name. This field can be blank. |
Address |
streetAddress |
The user’s street address. This field can be blank. |
City |
l |
The user’s city. This field can be blank. |
State/Province |
st |
The user’s state. This field can be blank. |
ZIP/Postal code |
postalCode |
The user’s ZIP/postal code. This field can be blank. |
Display picture |
jpegPhoto |
The user’s display picture. This field can be blank. |
After you create an AD/LDAP synchronizer, you can edit the associated fields at any time.
Refer to the Common AD/LDAP Field Mappings topic for information about field mappings between AD and LDAP.
Related Topics: