--- title: "Authentication using LDAP" slug: "authentication-using-ldap-3" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:29:17Z published: 2026-11-19T12:29:17Z canonical: "docs.trellix.com/authentication-using-ldap-3" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Authentication using LDAP The LDAP communication from the client Managers is over a secure communication. Therefore, LDAP configuration information is valid and can be passed onto all the Managers. The LDAP server configuration in the Central Manager should be synchronized with all Managers. If a LDAP configuration is done at the Central Manager, and no LDAP server exists at the Manager level, then after synchronization, the Manager will inherit the configuration with a suffix "Inherited". If the Manager has its own LDAP configuration, it will not inherit the configuration from the Central Manager level; it will have its own customized configuration with a suffix "Customized". At any time, if a user deletes the configuration made at the Manager level, the inherited configuration is displayed. For more information on configuring a LDAP server, see [Configuration of LDAP servers](/network-and-platform/docs/configuration-of-ldap-servers-2). > [!NOTE] > Note > > If LDAP servers are configured with the Central Manager, and the LDAP servers exist in private networks and Managers exist in public network, the LDAP configuration needs to be customized at the Manager in a way that it reaches the LDAP server through translated public IP address.