Documentation for Intellect 4.11.0-4.11.3. Documentation for other versions of Intellect is available too.

Previous page Configuration of the LDAP Service  Configuring the connection to the LDAP address book Next page


The LDAP Service module offers the ability to perform the following actions:

  1. Import data from an LDAP address book into the Intellect database.
  2. Synchronize the Intellect database with an LDAP address book.

Important!

All entries stored in an LDAP directory have uid (unique user id) and ou (department) attributes. If these attributes are absent, then LDAP service fails to import and synchronize users between LDAP address book and Intellect DB.

If other attributes are used as unique id and department name in the address book, then these attributes  are to be specified while configuring LDAP Service – see Configuration of correspondence between address attributes and Intellect DB fields.

When importing or synchronizing, users which have been manually created in the Intellect Software System before or after the import operation are not affected.

Importing data and synchronizing the Intellect database with an LDAP address book are accomplished using macros (the LDAP Service object's Get all employees action – see Example macro for user import from LDAP address book; see Creating and using macros for detailed information about macros). Use a Timer object for scheduled synchronization (see Creating and using the Timer object).

The following LDAP attributes are supported by Intellect:

LDAP attribute

Field in Intellect

Commentary

User

sn

Surname (the User object, the name parameter)

If there is no sn attribute in return data, then this entry is ignored.

Please note that the last name of the user is stored in the "name" field in the Intellect database.

givenname

Name (the User object, the surname parameter)

Please note that the first name of the user is stored in the "surname" field in the Intellect database.

uid

ID in the external DB (the User object, the, external_id parameter)

If there is no uid attribute in return data, then a new employee is created i.e. there is duplication of employee.

If another attribute is used as uid in the address book, then this attribute is to be specified while configuring LDAP Service – see Configuration of correspondence between address attributes and Intellect DB fields.

mailE-mail address (the User object, the email parameter)
telephoneNumber(the User object, the phone parameter)
title(the User object, the post parameter)

Department

ou

Department name (the Department object, the name parameter)

If another attribute is used as ou in the address book, then this attribute is to be specified while configuring LDAP Service – see Configuration of correspondence between address attributes and Intellect DB fields.
Group
groupUser group in Request type (see Configuring the connection to the LDAP address book)The attribute is used to import user groups when selecting the request type Group or Users and groups.
  • No labels