LDAP certificate settings

Prev Next

NOTE

Ensure that your LDAP server is configured 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.

Complete the following fields in the LDAP Configuration section of the Add/Edit Identity Provider page:

  • Hostnames or IP Addresses. Enter one or more hosts. If more then one host is entered, AppGate ZTNA choose one at random. This provides load balancing and failover. All remaining settings are assumed to be the same for all LDAP hosts.

  • Port. Enter 389 for LDAP or 636 for LDAP over SSL.

  • Enable SSL. SSL (LDAPS) is recommended. To use SSL, upload an X.509 public key certificate to Trusted Certificates (System > Trusted Certificates).

  • Service Account DN. The Service account must have the minimum rights required to read the tree below the base DN. For example: "CN=Administrator, OU=Admins, OU=Users, DC=corp, DC=yourdomain, DC=com"

  • Service Account Password. Password for the service account user.

  • Base DN. Distinguished Name of the user search base. This limits the scope of the user search to improve performance by avoiding searches across the entire directory.

  • User Filter. Include or exclude groups of user accounts. For example, “All disabled user objects” or “All users with ‘Password Never Expires’ set”. The following page provides more examples: https://social.technet.microsoft.com

  • Username Attribute. Attribute name of the username field. Defaults to sAMAccountName in Active Directory.

  • Membership Filter. Filter used when retrieving the user’s nested groups in Active Directory. Defaults to (objectCategory=group).

  • Membership Base DN. Distinguished Name of the group search base in Active Directory. This limits the scope of the membership query to improve performance. Defaults to the Base DN setting.

  • User Certificate Priority. Sets the order in which certificates appear in the client. An exact match in these fields determines the order. Some CAs issue certificates that include Issuer and Certificate Template Information fields. Select Template or Issuer, then enter the exact value from the certificate field. After you add entries, you can reorder the list. Certificates are then prioritized by Valid to date, with the furthest date prioritized.

  • CA Certificates. Upload CA certificates to verify client certificates. If the client certificate is signed by an intermediate CA, upload the full certificate chain. If the client certificate includes a valid AIA extension, the root certificate is sufficient.

NOTE

The Controller issues a warning in the dashboard 30 days before any certificates expire.

  • Skip X.509 external checks. When enabled, the Controller does not contact endpoints listed in certificate extensions to check revocation status or retrieve intermediate CA certificates. This is not recommended.

  • SAN Type. Select which Subject Alternative Name (SAN) of the client certificate to map to an LDAP user. Any is the default value and accepts any otherName, rfc822Name, or dNSName. UserPrincipalName matches only the otherName with OID 1.3.6.1.4.1.311.20.2.3.

  • Certificate User Attribute. Enter the LDAP attribute that maps to the Subject Alternative Name field. This is required to verify the username so the AppGate system can collect all the user’s LDAP attributes.

  • Verify certificate on LDAP. Enable to compare the presented public certificate with the certificate stored in LDAP at authentication. If they do not match, authentication fails.

    • Attribute. Enter the LDAP attribute that points to the users' certificates in LDAP. In Active Directory, this is typically userCertificate.