Lightweight Directory Access Protocol
ldapd is a daemon which implements version
3 of the LDAP protocol.
ldapd process can be controlled
using the ldapctl(8) utility.
The options are as follows:
- Define macro to be set to value on the command line. Overrides the definition of macro in the configuration file.
- Do not daemonize and log to stderr.
- Use file as the configuration file, instead of the default /etc/ldapd.conf.
- Configtest mode. Only check the configuration file for validity.
- Store and read database files in directory, instead of the default /var/db/ldap.
- Specify an alternative location for the socket file.
- Produce more verbose output. A second
-vtogether with the
-dflag produces debug traces of decoded BER messages on stderr.
ldapd can authenticate users via simple
binds or SASL with the PLAIN mechanism.
When using simple binds, the bind DN entry must exist in a
namespace and have a
userPassword attribute. The
following formats of the
userPassword attribute are
- Verify the password against the SHA-1 digest.
- Verify the password against the salted SHA-1 digest.
- Verify the password against the crypt(3) hash.
- Use BSD Authentication with the given username and authentication style “auth-ldap”. This is similar to using SASL PLAIN authentication with username as the authentication ID.
- Same as above, but overrides the login class.
Without a prefix, the
attribute is compared literally with the provided plain text password.
When using SASL binds, the authentication ID should be a valid username for BSD Authentication.
For plain text passwords to be accepted, the connection must be
considered secure, either by using an encrypted connection, or by using the
secure keyword in the configuration file.
ldap(1), ldapd.conf(5), login.conf(5), ldapctl(8)
J. Sermersheim, Lightweight Directory Access Protocol (LDAP): The Protocol, RFC 4511, June 2006.
K. Zeilenga, Lightweight Directory Access Protocol (LDAP): Directory Information Models, RFC 4512, June 2006.
ldapd program first appeared in
ldapd is not yet fully LDAPv3
Database files are not expected to work across architectures and may not work across versions.