•
• Add or select an LDAP Server Profile to configure settingsfor the Lightweight Directory Access Protocol (LDAP) servers that authentication profiles reference (see Device > Authentication Profile). You can use LDAP to authenticate end users who access your network resources (through GlobalProtect or Authentication Portal) and administrators defined locally on the firewall or Panorama.
Select the scope in which the profile is available. In the context of a firewall that has more than one virtual system (vsys), select a vsys or select Shared (all virtual systems). In any other context, you can’t select the Location; its value is predefined as Shared (firewalls) or as Panorama. After you save the profile, you can’t change its Location.
• 389 (default)—TLS (Specifically, the firewall uses the Start TLS operation, which upgrades the initial plaintext connection to TLS.)
•
• The certificate is trusted and valid. For the firewall to trust the certificate, its root certificate authority (CA) and any intermediate certificates must be in the certificate store under Device > Certificate Management > Certificates > Device Certificates.
• The certificate name must match the host Name of the LDAP server. The firewall first checks the certificate attribute Subject AltName for matching, then tries the attribute Subject DN. If the certificate uses the FQDN of the directory server, you must use the FQDN in the LDAP Server field for the name matching to succeed.If the verification fails, the connection fails. To enable this verification, you must also select Require SSL/TLS secured connection.