Active Directory (AD) Configuration Details

To successfully integrate the Eko Active Directory Connector (EkoADC) with your organization's directory service, the customer must provide specific configuration details related to their Active Directory (AD) or LDAP-compatible system. These details are necessary for Amity Solutions to configure the EkoADC software and enable secure synchronization and authentication processes.

1. Required AD Connection Details

The following information ensures EkoADC can establish and maintain communication with your on-premises Active Directory.

Configuration Detail	Example Value	Description
LDAP/Active Directory IP address	ldaps://x.x.x.x	The network address used by EkoADC to locate the AD server.
Protocol	LDAPS (Recommended)	Specifies the protocol used: LDAP or the secure version, LDAPS.
Port	636	The network port utilized for the connection (e.g., 636 for LDAPS or 389 for standard LDAP).
LDAP Username		The designated account used by EkoADC to bind and search the AD.
LDAP Password		The corresponding password for the LDAP Username.
Base DN	DC=EXAMPLE,DC=COM	The starting point (distinguished name) in the directory tree where EkoADC begins searching for users.
Group DN	DC=EXAMPLE,DC=COM (Optional)	Specifies a distinguished name if synchronization is required for users belonging to only a specific group.
Filter	(objectclass=user) (Optional)	A special filter that can be used to restrict the types of objects (e.g., only user accounts) that EkoADC synchronizes.

2. Required AD Attributes

For accurate user provisioning, EkoADC needs to map specific attributes from the Active Directory schema to the corresponding fields in the Eko Database. The customer must confirm which AD attributes will supply the necessary user data.

Required attributes include fields such as:

• Unique ID

• Username (e.g., sAMAccountName)

• Firstname (e.g., givenName)

• Lastname (e.g., sn)

• Email (e.g., mail)

• Telephone Number

• Office

• Title

• Department

• Company

These attributes enable features like mapping the sAMAccountName to the Eko fields username and network_uid.

For Eko Call integration, specific attributes such as ipPhone, pager, and telephoneNumber are also mapped to corresponding Eko Call fields like ext_number, class_of_service, and did_number.

3. Additional Configuration Parameters

The configuration may also include settings related to user data handling. However, these are typically managed by Amity Solutions:

• User Search Limit: Defines the maximum number of users fetched per search operation (e.g., 10000).

• Login Pattern.

• Time Offset.

• Proxy Configuration: If the EkoADC needs to communicate externally through a customer proxy, proxy details (protocol, host, port, username, password) are required in the proxy section of the configuration.