The username and password provided by each connection is forwarded to a remote LDAP(S) for authentication. For LDAP access, no master user or password is required.
Address (or domain name) and port number used to connect to the remote LDAP server.
Whether to use LDAPS / LDAP over TLS/SSL to connect to the server.
Defines the method used to construct the LDAP DN used for the LDAP authentication (BIND) request.
List of DNs used to construct the BIND DN or in which to search for LDAP accounts.
These configuration allows filtering the LDAP accounts that have access to SFTPPlus and the user data to be extracted from the LDAP server in order to server as the configuration for the authenticated user.
Name of the attribute used to generate the full BIND DN based on the provided username.
Value added after the username when making the LDAP authentication request. This is useful for defining a default Active Directory domain.
Name of the attribute used to extract the associated home folder from the LDAP entry after a successful BIND operation. Leave empty not to use LDAP data for the home folder configuration.
Name of the attribute used to extract the associated email from the LDAP. Leave empty not to retrieve user email from LDAP.
LDAP search filter expression used to exclude / include only a subset of the LDAP entries as file transfer accounts. Leave this field empty to accept any LDAP entry.
LDAP search filter expression used to exclude / include only a subset of the LDAP entries as Web Manager administrators. Leave this field empty to disable LDAP administrators.
These are advanced configuration options for integrating SFTPPlus with a wide range of LDAP servers. Get in touch with our support team to find out more about the capabilities of these configrations.
Entry point to the extension to be used during the LDAP authentication.
Configuration in JSON format for the selected extension.
Comma separated values of group configuration
mapped to LDAP attributes.
See
the documentation for more details
.