Documentation Index

Fetch the complete documentation index at: https://docs.knovvu.com/llms.txt

Use this file to discover all available pages before exploring further.

LDAP User Integration

  • Updated on Jul 29, 2026
  • Published on Jul 29, 2026
  • 3 minute(s) read
  • CA
 Prev Next

LDAP V2 User Integration – Setup & Configuration Guide

Feature: Multi-LDAP / Active Directory user synchronization (user-ldap-v2)
Audience: Deployment & configuration engineers, product operations

Overview

The user-ldap-v2 integration synchronizes users from one or more Active Directory (AD) / LDAP servers into a CA tenant. Conversational Analytics (CA) supports multiple integration instances for the same tenant, so users originating from different AD servers can be onboarded into a single tenant.

The end-to-end flow consists of four stages:

  1. Deploy the user-ldap-v2 integration service(s).
  2. Define the LDAP Server settings in the tenant.
  3. Configure each AD server integration (tenant selection + field mapping).
  4. Run the integration and verify that the expected users are created.

1. Deploy the integration service(s)

Deploy one or more user-ldap-v2 integration services. Each running service appears in the Service List as an active instance with its own Unique Key and status.

Each AD server is served by its own integration instance. In the example below, two instances are running — one bound to sunucu1 and one to sunucu2 — each reporting Integration.Service.Status.Running.

2. Define the LDAP Server settings

In the tenant, navigate to:

Tenant → Settings → Integration → LDAP Servers (v2) tab

Define an entry for every AD server that will be synchronized (e.g. sunucu1, sunucu2). These entries become the selectable LdapServerEntityId values used in the integration configuration in the next step.

3. Configure each AD server integration

For every defined AD server, create and configure an integration:

Host → Integrations → user-ldap-v2 (Config)

  1. Select the relevant tenant.
  2. Select the corresponding LdapServerEntityId (the LDAP server defined in step 2).
  3. Define the field mapping between AD attributes and Knovvu Analytics user fields.

Note: CA can define more than one integration for the same tenant. Repeat this configuration once per AD server so that all servers feed the same tenant.

Service Settings reference

The Service Settings panel exposes the following configuration parameters:

Setting Description Example / Default
TenantId Tenant the integration service works for. ca-edit
Interval Polling interval for the integration service (seconds). 3600 (default)
LdapServerEntityId The LDAP server defined in step 2 that this integration binds to. sunucu1 / sunucu2
LdapDirectory LDAP directory / base DN. No default value
GenericFields AD-to-Knovvu attribute mapping (see below). —
IgnoreDepartmentInformation If enabled, department data from AD is ignored. False (default)
IntegrationStartTime Optional start time (enable via Enable Start Time). Enter the time in UTC, not local time. No default value

Example field mapping (GenericFields)

Knovvu field AD attribute
UserName sAMAccountName
Email mail
Name givenName
Surname sn

Image

Service List showing two running Ldap V2 User Integration instances (sunucu1, sunucu2), with the Service Settings panel and the LdapServerEntityId dropdown exposing the defined LDAP servers.

Once configuration is complete, use Synchronize to trigger a sync, or Save to persist the settings.

4. Run the integration and verify the users

After the integration runs, verify that the expected users have been created under:

Administration → Users

For a synchronized user, confirm that:

  • The Ldap user flag is enabled.
  • The Auth source reflects the originating AD server (sunucu1 or sunucu2), matching the integration that created the user.
  • Core fields (Name, Username, E-mail, Department, External ID) are populated according to the field mapping defined in step 3.

Image

User detail page for a synchronized LDAP user. The Ldap user flag is enabled and the Auth source dropdown lists the available AD servers (sunucu1, sunucu2).

Summary checklist

  • user-ldap-v2 service(s) deployed and running (one instance per AD server)
  • LDAP Server settings defined per AD server (Tenant Settings → Integration → LDAP Servers (v2))
  • Integration configured per AD server (tenant selected, LdapServerEntityId bound, field mapping defined)
  • Multiple integrations pointing to the same tenant where required
  • Integration executed and synchronized users verified under Administration → Users (Ldap user + correct Auth source)