• Documentation
    • Search documentation
    karat

    +

    K

    API Reference ↗
    Data connectivity & integrationAvailable connectorsLDAP

    LDAP

    The LDAP connector is a Palantir-provided driver for LDAP.

    To create a new LDAP source, follow the standard setup flow for Palantir-provided drivers, then use the sections below for LDAP-specific configuration and networking. For the complete property reference, see the official LDAP driver documentation ↗.

    Configuration

    The properties below are mandatory or recommended.

    PropertyRequired?DescriptionDefault
    Server ↗MandatorySpecifies the domain name or IP address of the LDAP server. This property is required to establish a connection and does not need to include the LDAP:\\ prefix, only the server’s domain name or IP address.{serverAddress}
    UseSSL ↗MandatorySpecifies whether SSL is used to secure the connection to the LDAP server. Enabling this property ensures that communication between the client and server is encrypted.TRUE
    BaseDN ↗RecommendedSpecifies the base portion of the distinguished name (DN) to limit LDAP queries to a specific subtree within the directory. Using a base DN helps narrow the search scope and improve query performance, especially on large LDAP servers.—
    Password ↗RecommendedSpecifies the password associated with the distinguished name (DN) of the user account used for authentication with the LDAP server. This property is required when the server enforces authentication.—
    Port ↗RecommendedSpecifies the port number on which the LDAP server is running.636
    User ↗RecommendedSpecifies the distinguished name (DN) of the user account to be used for authentication with the LDAP server. This property is required when the server enforces authentication.—

    Networking

    The table below lists the domains that the source needs to be able to access in order to successfully run.

    For each domain, add a corresponding egress policy. If the source is hosted on-premises and not directly reachable from Foundry, use an agent proxy egress policy instead; the agent host itself must also be able to reach the listed domains. See using an agent as a proxy for details.

    DomainRequired
    <Server>:<Port>Always. Server and Port connection properties (default Port=636)