All LDAP connections must operate according to specified parameters, whose exact values are usually stored within the LDAP server configuration.
The LDAP URL (e.g., ldap://example.com/dc=jfrog,dc=org) uses the ldap or ldaps protocol (where the "s" stands for "secure" and uses SSL encryption). The dc or Directory Components section maps to an organization's top-level LDAP coordinates. In the example above, this translates as jfrog.org.
The search filter (e.g., samAccountName={0}) or user DN pattern (uid={0},ou=people) is how Artifactory searches for users in the LDAP system. The {0} is filled in with the username submitted. Either the search filter or the user DN pattern can be used, but at least one needs to be configured.
Although LDAP manager credentials (e.g., cn=admin,dc=example,dc=com) are not strictly required, they can be handy as most LDAP servers require authentication to look up directory information. In LDAP, this takes the form of LDAP coordinates, which are mapped to a username and a password.
The LDAP URL (e.g., ldap://example.com/dc=jfrog,dc=org) uses the ldap or ldaps protocol (where the "s" stands for "secure" and uses SSL encryption). The dc or Directory Components section maps to an organization's top-level LDAP coordinates. In the example above, this translates as jfrog.org.
The search filter (e.g., samAccountName={0}) or user DN pattern (uid={0},ou=people) is how Artifactory searches for users in the LDAP system. The {0} is filled in with the username submitted. Either the search filter or the user DN pattern can be used, but at least one needs to be configured.
Although LDAP manager credentials (e.g., cn=admin,dc=example,dc=com) are not strictly required, they can be handy as most LDAP servers require authentication to look up directory information. In LDAP, this takes the form of LDAP coordinates, which are mapped to a username and a password.