--- title: "LDAP provider" slug: "ldap-provider-v7-0" description: "Learn how AppGate integrates with LDAP IdPs like Active Directory for secure user authentication and efficient load balancing." tags: ["IdP Configuration", "LDAP Provider", "Identity Providers"] updated: 2026-06-05T19:17:41Z published: 2026-06-05T19:17:41Z canonical: "support.appgate.com/ldap-provider-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # LDAP provider This section describes how AppGate ZTNA works with LDAP identity providers (IdPs). AppGate ZTNA supports standard enterprise IdPs such as Active Directory (Entra ID). These IdPs authenticate users who connect through the client and administrators who sign in to the Controller Management interface. By specifying multiple LDAP servers, AppGate ZTNA selects one at random, providing LDAP load balancing and failover. --- ## Operation of LDAP providers With this IdP type: - The client passes the user's credentials to the Controller. - The service account (bind account) locates the user in AD. The service account is required because the username alone is not sufficient to bind. - This provides the Controller with the `userPrincipalName` for the user. - Using that information, the Controller binds using the username and password. - If the bind is successful, the user is authenticated successfully. - The Controller then queries AD for attributes and group memberships. --- ## Prerequisites of LDAP providers Configure your LDAP server for encrypted communication. If SSL is enabled and the LDAP server has a valid certificate, the Controller automatically establishes an encrypted session with the directory server. --- ## Shortening lookup times with LDAP providers If an AppGate system relies on Active Directory (AD) group memberships, perform an audit of both user and machine group memberships before deployment. This audit helps clean up the directory structure and optimizes lookup performance. ### Why lookup times matter Lookup times directly affect authentication behavior: - The Controller waits up to five seconds for a response from the LDAP server. - If multiple LDAP servers are configured, the Controller moves to the next server after five seconds. - If only one LDAP server is configured, the Controller waits up to ten seconds. - Headless clients retry sign-in continuously until authentication succeeds. In environments with many headless clients, repeated retries can flood Controllers with sign-in requests, which compounds any latency or availability issues in the directory servers. ### Reducing lookup times through IdP configuration To keep lookup times as short as possible, fully configure the identity provider. Specifically, use the ***Base DN***, ***Membership Base DN***, and ***Membership Filter*** fields to limit the scope of LDAP searches. If these fields are not configured, LDAP searches span the entire directory tree, significantly increasing lookup time. - ***Base DN***. Defines the portion of the LDAP tree that contains users. It may also include user groups, but the smaller the Base DN, the better the lookup performance. - ***Membership Base DN***. Defines the portion of the LDAP tree that includes user groups. After a user is authenticated, the Controller performs a second LDAP query using this value to identify group memberships. If nothing is defined in this field, the Controller uses the Base DN. - ***Membership Filter***. Further restricts the group search. Any filter configured here is concatenated with the search base and applied during the Controller’s group lookup query. Using a Membership Filter limits the number of objects evaluated, which helps reduce lookup times even further. ### Group resolution behavior How group membership is resolved depends on how Base DN is defined: - If ***Base DN*** includes only users, group membership is derived solely from the user record. For example: - The user record might list only `sweden-sales` - Nested group relationships, such as `sweden-sales` > `sales` > `commercial`, are not discovered. - If ***Base DN*** includes both users and groups, group membership is derived from group records. - The user is correctly identified as a member of `sweden-sales`, `sales`, and `commercial`. ### Using Membership Base DN for performance and accuracy Using ***Membership Base DN*** allows the ***Base DN*** to be minimized, which reduces the scope of the initial user search and shortens lookup times. Group searches are then performed against ***Membership Base DN***, ensuring that all relevant group memberships— including nested groups—are returned. This approach also reduces the scope of the second group lookup, further improving performance. ### Using mulitple IdPs to shorten lookup times The use of multiple IdPs can also minimize lookup times. If you have two different classes of users, such as human users with full clients and headless clients, you can create two different IdPs and use different ***Base DN***, ***Membership Filter***, and/or ***Membership Base DN*** values against an optimized tree structure. If your users were everywhere but the headless client users were recently added, then a filter like `objectCategory=appgate-headless.*` could be used. The following is an example of an LDAP configuration: #### ![Configuration settings for user filters and membership base for an LDAP identity provider.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/ag62-ldap_example.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A49%3A39Z&se=2026-11-21T22%3A49%3A39Z&sr=b&sp=r&sig=Q6vSyw5mChIXaQas1c1xoKTwU7QRTwfdLrXn85O7Wd4%3D) --- ## Client authentication with an LDAP provider - **Client sign-in**. When an LDAP IdP has been selected on the client sign-in screen, enter the username and password. If *Keep me signed in* is selected, the client remembers the credentials and uses them to auto-start the next time the user signs in. The Controller maps attributes based on the entered username to populate user claims, and issues claims and entitlement tokens. - **Claims token renewal**. When the user's claims token expires, the client uses the cached username and password to renew the token automatically. If the credentials no longer match, the user is prompted to reauthenticate to renew the token. - **Password user interaction**. If a password [user interaction](/v1/docs/applying-access-controls-v7-0#user-interactions) is triggered, the client prompts the user to enter a password. This password might be for the IdP used to sign in, or it might be for a different IdP. ### Administrator authentication with an LDAP provider These methods can also authenticate an administrator who signs in to the Controller admin UI and for REST API calls.