Extensions > Standard extensions / Active Directory/LDAP

Active Directory/LDAP

Active Directory/LDAP standard extension allows you to import users from another corporate system to ELMA365 while retaining their login information. Imported and manually registered users can work in ELMA365 system simultaneously.

How it works

The system administrator connects an AD/LDAP server to ELMA365 using the server address, login and password. Then, he or she defines the correspondence between ELMA and AD/LDAP fields and a database synchronization interval. Next, the AD/LDAP server is added to the Integration list. The users can be imported directly to ELMA365. Then, the employees will be able to log in using their username and password from the system from which they were imported.  

That way, you can configure integration with multiple systems.

Configuration

To configure the AD/LDAP integration, go to the Administration >Extensions.

ADLDAPI1

Select the Active Directory or LDAP and check the Enable integration box. To add a new item, click Add item.

The properties window opens.

1. Connect to the server

First, set up the connection between ELMA365 and the AD/LDAP server.

ADLDAPI2

Name*. Enter the Name of the integration. It will be displayed in the integration list.

Server address*. Enter the external server address.

User*. Enter the user name for LDAP server authentication.

Password*. Enter the user password.

Next, fill in the user connection and import fields.

2. User connection and import

начало внимание

When you set up the Active Directory integration, the following fields are filled in automatically. In case of LDAP integration, you have to fill in the fields manually.

конец внимание

ADLDAPI3

Authorization template. Enter the domain name for the external server. If necessary, you can add the user login, for example company\{$login}.

Path to users. Specify a path to users using the ADSI connection string syntax:

OU – stands for Organization Unit that contains such objects as users, contacts, groups, and others.

CN – stands for Common Name that is a name of a user, contact, group, or another object that usually does not have child objects.

DC – stands for Domain Component that is the name of the domain or the DNS.

For example, in order to import the users from the Users root group of the company .local domain, use the following path: “cn=Users, dc=company, dc=local”.

User Import filter. Filter used in queries to LDAP server when importing users.

Next, map the ELMA and LDAP fields:

Login parameter. Specify the field storing the user login on the LDAP server, for example, "sAMAccountName". After the user is imported from LDAP he or she authenticates in ELMA365 under this name;

Name parameter. Specify the field storing the user name on the LDAP server, for example, "name";

Configure the Surname, Initials, Telephone number, Mobile telephone number, E-mail parameters in the same way.

3. Automation settings

ADLDAPI4

Here, you can turn on or off the automatic user synchronization and import.

Synchronization automatically transfers all changes from AD/LDAP accounts to the associated ELMA365 accounts. Locked users, name or phone change, other personal data, for example.

Autoimport automatically imports new users from AD/LDAP to ELMA365 at synchronization.

Set the synchronization frequency in minutes according to your company rules.