1 .TH SLAPD.CONF 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2007 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapd.conf \- configuration file for slapd, the stand-alone LDAP daemon
12 contains configuration information for the
14 daemon. This configuration file is also used by the
16 replication daemon and by the SLAPD tools
28 file consists of a series of global configuration options that apply to
30 as a whole (including all backends), followed by zero or more database
31 backend definitions that contain information specific to a backend
33 The configuration options are case-insensitive;
34 their value, on a case by case basis, may be case-sensitive.
41 # comment - these options apply to every database
42 <global configuration options>
43 # first database definition & configuration options
44 database <backend 1 type>
45 <configuration options specific to backend 1>
46 # subsequent database definitions & configuration options
50 As many backend-specific sections as desired may be included. Global
51 options can be overridden in a backend (for options that appear more
52 than once, the last appearance in the
56 If a line begins with white space, it is considered a continuation
57 of the previous line. Blank lines and comment lines beginning with
58 a `#' character are ignored. Note: continuation lines are unwrapped
59 before comment processing is applied.
61 Arguments on configuration lines are separated by white space. If an
62 argument contains white space, the argument should be enclosed in
63 double quotes. If an argument contains a double quote (`"') or a
64 backslash character (`\\'), the character should be preceded by a
67 The specific configuration options available are discussed below in the
68 Global Configuration Options, General Backend Options, and General Database
69 Options. Backend-specific options are discussed in the
71 manual pages. Refer to the "OpenLDAP Administrator's Guide" for more
72 details on the slapd configuration file.
73 .SH GLOBAL CONFIGURATION OPTIONS
74 Options described in this section apply to all backends, unless specifically
75 overridden in a backend definition. Arguments that should be replaced by
76 actual text are shown in brackets <>.
78 .B access to <what> "[ by <who> <access> <control> ]+"
79 Grant access (specified by <access>) to a set of entries and/or
80 attributes (specified by <what>) by one or more requestors (specified
82 If no access controls are present, the default policy
83 allows anyone and everyone to read anything but restricts
84 updates to rootdn. (e.g., "access to * by * read").
85 The rootdn can always read and write EVERYTHING!
88 and the "OpenLDAP's Administrator's Guide" for details.
91 Specify a set of features (separated by white space) to
94 allows acceptance of LDAPv2 bind requests. Note that
96 does not truly implement LDAPv2 (RFC 1777), now Historic (RFC 3494).
98 allows anonymous bind when credentials are not empty (e.g.
101 allows unauthenticated (anonymous) bind when DN is not empty.
103 allows unauthenticated (anonymous) update operations to be processed
104 (subject to access controls and other administrative limits).
106 .B argsfile <filename>
107 The ( absolute ) name of a file that will hold the
109 server's command line options
110 if started without the debugging command line option.
112 .B attributeoptions [option-name]...
113 Define tagging attribute options or option tag/range prefixes.
114 Options must not end with `-', prefixes must end with `-'.
115 The `lang-' prefix is predefined.
118 directive, `lang-' will no longer be defined and you must specify it
119 explicitly if you want it defined.
121 An attribute description with a tagging option is a subtype of that
122 attribute description without the option.
123 Except for that, options defined this way have no special semantics.
124 Prefixes defined this way work like the `lang-' options:
125 They define a prefix for tagging options starting with the prefix.
126 That is, if you define the prefix `x-foo-', you can use the option
128 Furthermore, in a search or compare, a prefix or range name (with
129 a trailing `-') matches all options starting with that name, as well
130 as the option with the range name sans the trailing `-'.
131 That is, `x-foo-bar-' matches `x-foo-bar' and `x-foo-bar-baz'.
133 RFC 4520 reserves options beginning with `x-' for private experiments.
134 Other options should be registered with IANA, see RFC 4520 section 3.5.
135 OpenLDAP also has the `binary' option built in, but this is a transfer
136 option, not a tagging option.
139 .B attributetype "(\ <oid>\
141 [DESC\ <description>]\
150 [NO\-USER\-MODIFICATION]\
151 [USAGE\ <attributeUsage>]\ )"
153 Specify an attribute type using the LDAPv3 syntax defined in RFC 4512.
154 The slapd parser extends the RFC 4512 definition by allowing string
155 forms as well as numeric OIDs to be used for the attribute OID and
156 attribute syntax OID.
162 .B authz-policy <policy>
163 Used to specify which rules to use for Proxy Authorization. Proxy
164 authorization allows a client to authenticate to the server using one
165 user's credentials, but specify a different identity to use for authorization
166 and access control purposes. It essentially allows user A to login as user
167 B, using user A's password.
170 flag disables proxy authorization. This is the default setting.
173 flag will use rules in the
175 attribute of the authorization DN.
178 flag will use rules in the
180 attribute of the authentication DN.
183 flag, an alias for the deprecated value of
185 will allow any of the above, whatever succeeds first (checked in
191 flag requires both authorizations to succeed.
194 The rules are mechanisms to specify which identities are allowed
195 to perform proxy authorization.
198 attribute in an entry specifies which other users
199 are allowed to proxy login to this entry. The
202 an entry specifies which other users this user can authorize as. Use of
205 abused if users are allowed to write arbitrary values to this attribute.
208 attribute must be protected with ACLs such that
209 only privileged users can modify it.
216 or a set of identities; it can take five forms:
219 .B ldap:///<base>??[<scope>]?<filter>
222 .B dn[.<dnstyle>]:<pattern>
225 .B u[<mech>[<realm>]]:<pattern>
228 .B group[/objectClass[/attributeType]]:<pattern>
235 .B <dnstyle>:={exact|onelevel|children|subtree|regex}
238 The first form is a valid LDAP
246 portions must be absent, so that the search occurs locally on either
252 with the optional style modifiers
258 for exact, onelevel, children and subtree matches, which cause
260 to be normalized according to the DN normalization rules, or the special
262 style, which causes the
264 to be treated as a POSIX (''extended'') regular expression, as
271 means any non-anonymous DN.
272 The third form is a SASL
274 with the optional fields
278 that allow to specify a SASL
280 and eventually a SASL
282 for those mechanisms that support one.
283 The need to allow the specification of a mechanism is still debated,
284 and users are strongly discouraged to rely on this possibility.
285 The fourth form is a group specification, consisting of the keyword
287 optionally followed by the specification of the group
293 is searched with base scope, and in case of match, the values of the
296 are searched for the asserted DN.
297 For backwards compatibility, if no identity type is provided, i.e. only
301 is assumed; as a consequence,
303 is subjected to DN normalization.
304 Since the interpretation of
308 can impact security, users are strongly encouraged
309 to explicitly set the type of identity specification that is being used.
310 A subset of these rules can be used as third arg in the
312 statement (see below); significantly, the
319 .B authz-regexp <match> <replace>
320 Used by the authentication framework to convert simple user names,
321 such as provided by SASL subsystem, to an LDAP DN used for
322 authorization purposes. Note that the resultant DN need not refer
323 to an existing entry to be considered valid. When an authorization
324 request is received from the SASL subsystem, the SASL
329 are taken, when available, and combined into a name of the form
333 .B UID=<username>[[,CN=<realm>],CN=<mechanism>],CN=auth
336 This name is then compared against the
338 POSIX (''extended'') regular expression, and if the match is successful,
339 the name is replaced with the
341 string. If there are wildcard strings in the
343 regular expression that are enclosed in parenthesis, e.g.
349 then the portion of the name that matched the wildcard will be stored
350 in the numbered placeholder variable $1. If there are other wildcard strings
351 in parenthesis, the matching strings will be in $2, $3, etc. up to $9. The
352 placeholders can then be used in the
357 .B UID=$1,OU=Accounts,DC=example,DC=com
360 The replaced name can be either a DN, i.e. a string prefixed by "dn:",
362 If the latter, the server will use the URI to search its own database(s)
363 and, if the search returns exactly one entry, the name is
364 replaced by the DN of that entry. The LDAP URI must have no
365 hostport, attrs, or extensions components, but the filter is mandatory,
369 .B ldap:///OU=Accounts,DC=example,DC=com??one?(UID=$1)
372 The protocol portion of the URI must be strictly
374 Note that this search is subject to access controls. Specifically,
375 the authentication identity must have "auth" access in the subject.
379 options can be given in the configuration file to allow for multiple matching
380 and replacement patterns. The matching patterns are checked in the order they
381 appear in the file, stopping at the first successful match.
384 .\"Because the plus sign + is a character recognized by the regular expression engine,
385 .\"and it will appear in names that include a REALM, be careful to escape the
386 .\"plus sign with a backslash \\+ to remove the character's special meaning.
389 .B concurrency <integer>
390 Specify a desired level of concurrency. Provided to the underlying
391 thread system as a hint. The default is not to provide any hint.
393 .B conn_max_pending <integer>
394 Specify the maximum number of pending requests for an anonymous session.
395 If requests are submitted faster than the server can process them, they
396 will be queued up to this limit. If the limit is exceeded, the session
397 is closed. The default is 100.
399 .B conn_max_pending_auth <integer>
400 Specify the maximum number of pending requests for an authenticated session.
403 .B defaultsearchbase <dn>
404 Specify a default search base to use when client submits a
405 non-base search request with an empty base DN.
406 Base scoped search requests with an empty base DN are not affected.
408 .B disallow <features>
409 Specify a set of features (separated by white space) to
410 disallow (default none).
412 disables acceptance of anonymous bind requests. Note that this setting
413 does not prohibit anonymous directory access (See "require authc").
415 disables simple (bind) authentication.
417 disables forcing session to anonymous status (see also
418 .BR tls_authc ) upon StartTLS operation receipt.
420 dissallow the StartTLS operation if authenticated (see also
424 .B ditcontentrule "(\ <oid>\
426 [DESC\ <description>]\
433 Specify an DIT Content Rule using the LDAPv3 syntax defined in RFC 4512.
434 The slapd parser extends the RFC 4512 definition by allowing string
435 forms as well as numeric OIDs to be used for the attribute OID and
436 attribute syntax OID.
442 .B gentlehup { on | off }
443 A SIGHUP signal will only cause a 'gentle' shutdown-attempt:
445 will stop listening for new connections, but will not close the
446 connections to the current clients. Future write operations return
447 unwilling-to-perform, though. Slapd terminates when all clients
448 have closed their connections (if they ever do), or \- as before \-
449 if it receives a SIGTERM signal. This can be useful if you wish to
450 terminate the server and start a new
453 .B with another database,
454 without disrupting the currently active clients.
455 The default is off. You may wish to use
457 along with this option.
459 .B idletimeout <integer>
460 Specify the number of seconds to wait before forcibly closing
461 an idle client connection. A idletimeout of 0 disables this
462 feature. The default is 0.
464 .B include <filename>
465 Read additional configuration information from the given file before
466 continuing with the next line of the current file.
468 .B index_substr_if_minlen <integer>
469 Specify the minimum length for subinitial and subfinal indices. An
470 attribute value must have at least this many characters in order to be
471 processed by the indexing functions. The default is 2.
473 .B index_substr_if_maxlen <integer>
474 Specify the maximum length for subinitial and subfinal indices. Only
475 this many characters of an attribute value will be processed by the
476 indexing functions; any excess characters are ignored. The default is 4.
478 .B index_substr_any_len <integer>
479 Specify the length used for subany indices. An attribute value must have
480 at least this many characters in order to be processed. Attribute values
481 longer than this length will be processed in segments of this length. The
482 default is 4. The subany index will also be used in subinitial and
483 subfinal index lookups when the filter string is longer than the
484 .I index_substr_if_maxlen
487 .B index_substr_any_step <integer>
488 Specify the steps used in subany index lookups. This value sets the offset
489 for the segments of a filter string that are processed for a subany index
490 lookup. The default is 2. For example, with the default values, a search
491 using this filter "cn=*abcdefgh*" would generate index lookups for
492 "abcd", "cdef", and "efgh".
494 .\"-- NEW_LOGGING option --
496 .\".B logfile <filename>
497 .\"Specify a file for recording debug log messages. By default these messages
498 .\"only go to stderr and are not recorded anywhere else. Specifying a logfile
499 .\"copies messages to both stderr and the logfile.
502 Specifies the Security Strength Factor (SSF) to be given local LDAP sessions,
503 such as those to the ldapi:// listener. For a description of SSF values,
507 option description. The default is 71.
509 .B loglevel <integer> [...]
510 Specify the level at which debugging statements and operation
511 statistics should be syslogged (currently logged to the
513 LOG_LOCAL4 facility).
514 They must be considered subsystems rather than increasingly verbose
516 Some messages with higher priority are logged regardless
517 of the configured loglevel as soon as some logging is configured,
518 otherwise anything is logged at all.
519 Log levels are additive, and available levels are:
530 debug packet handling
534 heavy trace debugging (function args)
538 connection management
542 print out packets sent and received
546 search filter processing
550 configuration file processing
554 access control list processing
558 stats log connections/operations/results
562 stats log entries sent
566 print communication with shell backends
578 data indexing (unused)
586 only messages that get logged whatever log level is set
589 The desired log level can be input as a single integer that combines
590 the (ORed) desired levels, both in decimal or in hexadecimal notation,
591 as a list of integers (that are ORed internally),
592 or as a list of the names that are shown between brackets, such that
605 can be used as a shortcut to enable logging at all levels (equivalent to -1).
608 or the equivalent integer representation, causes those messages
609 that are logged regardless of the configured loglevel to be logged.
610 In fact, if no loglevel (or a 0 level) is defined, no logging occurs,
613 level is required to have high priority messages logged.
616 .B moduleload <filename>
617 Specify the name of a dynamically loadable module to load. The filename
618 may be an absolute path name or a simple filename. Non-absolute names
619 are searched for in the directories specified by the
621 option. This option and the
623 option are only usable if slapd was compiled with --enable-modules.
625 .B modulepath <pathspec>
626 Specify a list of directories to search for loadable modules. Typically
627 the path is colon-separated but this depends on the operating system.
630 .B objectclass "(\ <oid>\
632 [DESC\ <description>]\
635 [{ ABSTRACT | STRUCTURAL | AUXILIARY }]\
636 [MUST\ <oids>] [MAY\ <oids>] )"
638 Specify an objectclass using the LDAPv3 syntax defined in RFC 4512.
639 The slapd parser extends the RFC 4512 definition by allowing string
640 forms as well as numeric OIDs to be used for the object class OID.
644 description.) Object classes are "STRUCTURAL" by default.
647 .B objectidentifier <name> "{ <oid> | <name>[:<suffix>] }"
648 Define a string name that equates to the given OID. The string can be used
649 in place of the numeric OID in objectclass and attribute definitions. The
650 name can also be used with a suffix of the form ":xx" in which case the
651 value "oid.xx" will be used.
653 .B password-hash <hash> [<hash>...]
654 This option configures one or more hashes to be used in generation of user
655 passwords stored in the userPassword attribute during processing of
656 LDAP Password Modify Extended Operations (RFC 3062).
657 The <hash> must be one of
671 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
676 use the MD5 algorithm (RFC 1321), the latter with a seed.
683 indicates that the new password should be
684 added to userPassword as clear text.
686 Note that this option does not alter the normal user applications
687 handling of userPassword during LDAP Add, Modify, or other LDAP operations.
689 .B password\-crypt\-salt\-format <format>
690 Specify the format of the salt passed to
692 when generating {CRYPT} passwords (see
694 during processing of LDAP Password Modify Extended Operations (RFC 3062).
696 This string needs to be in
698 format and may include one (and only one) %s conversion.
699 This conversion will be substituted with a string of random
700 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
701 provides a two character salt and "$1$%.8s" tells some
702 versions of crypt(3) to use an MD5 algorithm and provides
703 8 random characters of salt. The default is "%s", which
704 provides 31 characters of salt.
706 .B pidfile <filename>
707 The ( absolute ) name of a file that will hold the
709 server's process ID ( see
711 ) if started without the debugging command line option.
714 Specify the referral to pass back when
716 cannot find a local database to handle a request.
717 If specified multiple times, each url is provided.
720 The ( absolute ) name of a file that will hold the
722 server's command line options
723 if started without the debugging command line option.
726 The ( absolute ) name of a file that will hold the
728 server's process ID ( see
730 ) if started without the debugging command line option.
732 .B replicationinterval
733 The number of seconds
735 waits before checking the replogfile for changes.
737 .B require <conditions>
738 Specify a set of conditions (separated by white space) to
739 require (default none).
740 The directive may be specified globally and/or per-database;
741 databases inherit global conditions, so per-database specifications
744 requires bind operation prior to directory operations.
746 requires session to be using LDAP version 3.
748 requires authentication prior to directory operations.
750 requires SASL authentication prior to directory operations.
752 requires strong authentication prior to directory operations.
753 The strong keyword allows protected "simple" authentication
754 as well as SASL authentication.
756 may be used to require no conditions (useful to clear out globally
757 set conditions within a particular database); it must occur first
758 in the list of conditions.
760 .B reverse-lookup on | off
761 Enable/disable client name unverified reverse lookup (default is
763 if compiled with --enable-rlookups).
766 Specify the name of an LDIF(5) file containing user defined attributes
767 for the root DSE. These attributes are returned in addition to the
768 attributes normally produced by slapd.
771 Used to specify the fully qualified domain name used for SASL processing.
773 .B sasl-realm <realm>
774 Specify SASL realm. Default is empty.
776 .B sasl-secprops <properties>
777 Used to specify Cyrus SASL security properties.
780 flag (without any other properties) causes the flag properties
781 default, "noanonymous,noplain", to be cleared.
784 flag disables mechanisms susceptible to simple passive attacks.
787 flag disables mechanisms susceptible to active attacks.
790 flag disables mechanisms susceptible to passive dictionary attacks.
793 flag disables mechanisms which support anonymous login.
796 flag require forward secrecy between sessions.
799 require mechanisms which pass client credentials (and allow
800 mechanisms which can pass credentials to do so).
803 property specifies the minimum acceptable
804 .I security strength factor
805 as an integer approximate to effective key length used for
806 encryption. 0 (zero) implies no protection, 1 implies integrity
807 protection only, 56 allows DES or other weak ciphers, 112
808 allows triple DES and other strong ciphers, 128 allows RC4,
809 Blowfish and other modern strong ciphers. The default is 0.
812 property specifies the maximum acceptable
813 .I security strength factor
814 as an integer (see minssf description). The default is INT_MAX.
817 property specifies the maximum security layer receive buffer
818 size allowed. 0 disables security layers. The default is 65536.
821 Specify the distinguished name for the subschema subentry that
822 controls the entries on this server. The default is "cn=Subschema".
824 .B security <factors>
825 Specify a set of security strength factors (separated by white space)
829 option for a description of security strength factors).
830 The directive may be specified globally and/or per-database.
832 specifies the overall security strength factor.
834 specifies the transport security strength factor.
836 specifies the TLS security strength factor.
838 specifies the SASL security strength factor.
840 specifies the overall security strength factor to require for
842 .B update_transport=<n>
843 specifies the transport security strength factor to require for
846 specifies the TLS security strength factor to require for
849 specifies the SASL security strength factor to require for
852 specifies the security strength factor required for
854 username/password authentication.
857 factor is measure of security provided by the underlying transport,
858 e.g. ldapi:// (and eventually IPSEC). It is not normally used.
860 .B sizelimit {<integer>|unlimited}
862 .B sizelimit size[.{soft|hard|unchecked}]=<integer> [...]
863 Specify the maximum number of entries to return from a search operation.
864 The default size limit is 500.
867 to specify no limits.
868 The second format allows a fine grain setting of the size limits.
869 Extra args can be added on the same line.
872 for an explanation of the different flags.
874 .B sockbuf_max_incoming <integer>
875 Specify the maximum incoming LDAP PDU size for anonymous sessions.
876 The default is 262143.
878 .B sockbuf_max_incoming_auth <integer>
879 Specify the maximum incoming LDAP PDU size for authenticated sessions.
880 The default is 4194303.
883 Specify the maximum size of the primary thread pool.
884 The default is 16; the minimum value is 2.
886 .B timelimit {<integer>|unlimited}
888 .B timelimit time[.{soft|hard}]=<integer> [...]
889 Specify the maximum number of seconds (in real time)
891 will spend answering a search request. The default time limit is 3600.
894 to specify no limits.
895 The second format allows a fine grain setting of the time limits.
896 Extra args can be added on the same line.
899 for an explanation of the different flags.
901 .B tool-threads <integer>
902 Specify the maximum number of threads to use in tool mode.
903 This should not be greater than the number of CPUs in the system.
905 .\"ucdata-path is obsolete / ignored...
907 .\".B ucdata-path <path>
908 .\"Specify the path to the directory containing the Unicode character
909 .\"tables. The default path is DATADIR/ucdata.
913 is built with support for Transport Layer Security, there are more options
916 .B TLSCipherSuite <cipher-suite-spec>
917 Permits configuring what ciphers will be accepted and the preference order.
918 <cipher-suite-spec> should be a cipher specification for OpenSSL. Example:
920 TLSCipherSuite HIGH:MEDIUM:+SSLv2
922 To check what ciphers a given spec selects, use:
924 openssl ciphers -v <cipher-suite-spec>
926 .B TLSCACertificateFile <filename>
927 Specifies the file that contains certificates for all of the Certificate
932 .B TLSCACertificatePath <path>
933 Specifies the path of a directory that contains Certificate Authority
934 certificates in separate individual files. Usually only one of this
935 or the TLSCACertificateFile is used.
937 .B TLSCertificateFile <filename>
938 Specifies the file that contains the
942 .B TLSCertificateKeyFile <filename>
943 Specifies the file that contains the
945 server private key that matches the certificate stored in the
946 .B TLSCertificateFile
947 file. Currently, the private key must not be protected with a password, so
948 it is of critical importance that it is protected carefully.
950 .B TLSDHParamFile <filename>
951 This directive specifies the file that contains parameters for Diffie-Hellman
952 ephemeral key exchange. This is required in order to use a DSA certificate on
953 the server. If multiple sets of parameters are present in the file, all of
954 them will be processed. Note that setting this option may also enable
955 Anonymous Diffie-Hellman key exchanges in certain non-default cipher suites.
956 You should append "!ADH" to your cipher suites if you have changed them
957 from the default, otherwise no certificate exchanges or verification will
960 .B TLSRandFile <filename>
961 Specifies the file to obtain random bits from when /dev/[u]random
962 is not available. Generally set to the name of the EGD/PRNGD socket.
963 The environment variable RANDFILE can also be used to specify the filename.
965 .B TLSVerifyClient <level>
966 Specifies what checks to perform on client certificates in an
967 incoming TLS session, if any.
970 can be specified as one of the following keywords:
976 will not ask the client for a certificate.
979 The client certificate is requested. If no certificate is provided,
980 the session proceeds normally. If a bad certificate is provided,
981 it will be ignored and the session proceeds normally.
984 The client certificate is requested. If no certificate is provided,
985 the session proceeds normally. If a bad certificate is provided,
986 the session is immediately terminated.
988 .B demand | hard | true
989 These keywords are all equivalent, for compatibility reasons.
990 The client certificate is requested. If no certificate is provided,
991 or a bad certificate is provided, the session is immediately terminated.
993 Note that a valid client certificate is required in order to use the
994 SASL EXTERNAL authentication mechanism with a TLS session. As such,
997 setting must be chosen to enable SASL EXTERNAL authentication.
1000 .B TLSCRLCheck <level>
1001 Specifies if the Certificate Revocation List (CRL) of the CA should be
1002 used to verify if the client certificates have not been revoked. This
1004 .B TLSCACertificatePath
1005 parameter to be set.
1007 can be specified as one of the following keywords:
1011 No CRL checks are performed
1014 Check the CRL of the peer certificate
1017 Check the CRL for a whole certificate chain
1019 .SH GENERAL BACKEND OPTIONS
1020 Options in this section only apply to the configuration file section
1021 for the specified backend. They are supported by every
1024 .B backend <databasetype>
1025 Mark the beginning of a backend definition. <databasetype>
1043 depending on which backend will serve the database.
1045 .SH GENERAL DATABASE OPTIONS
1046 Options in this section only apply to the configuration file section
1047 for the database in which they are defined. They are supported by every
1048 type of backend. Note that the
1052 option are mandatory for each database.
1054 .B database <databasetype>
1055 Mark the beginning of a new database instance definition. <databasetype>
1073 depending on which backend will serve the database.
1078 will automatically maintain the
1079 modifiersName, modifyTimestamp, creatorsName, and
1080 createTimestamp attributes for entries. It also controls
1081 the entryCSN and entryUUID attributes, which are needed
1082 by the syncrepl provider. By default, lastmod is on.
1084 .B limits <who> <limit> [<limit> [...]]
1085 Specify time and size limits based on who initiated an operation.
1092 anonymous | users | [dn[.<style>]=]<pattern> | group[/oc[/at]]=<pattern>
1098 <style> ::= exact | base | onelevel | subtree | children | regex | anonymous
1103 matches all unauthenticated clients.
1106 matches all authenticated clients;
1109 dn pattern is assumed unless otherwise specified by qualifying
1110 the (optional) key string
1116 (which are synonyms), to require an exact match; with
1118 to require exactly one level of depth match; with
1120 to allow any level of depth match, including the exact match; with
1122 to allow any level of depth match, not including the exact match;
1124 explicitly requires the (default) match based on POSIX (''extended'')
1125 regular expression pattern.
1128 matches unbound operations; the
1131 The same behavior is obtained by using the
1138 with the optional objectClass
1144 sets the limits for any DN listed in the values of the
1150 group objectClass (default
1152 whose DN exactly matches
1155 The currently supported limits are
1160 The syntax for time limits is
1161 .BR time[.{soft|hard}]=<integer> ,
1164 is the number of seconds slapd will spend answering a search request.
1165 If no time limit is explicitly requested by the client, the
1167 limit is used; if the requested time limit exceeds the
1170 .\".I "Administrative limit exceeded"
1171 .\"error is returned.
1172 limit, the value of the limit is used instead.
1175 limit is set to the keyword
1177 the soft limit is used in either case; if it is set to the keyword
1179 no hard limit is enforced.
1180 Explicit requests for time limits smaller or equal to the
1183 If no limit specifier is set, the value is assigned to the
1189 to preserve the original behavior.
1191 The syntax for size limits is
1192 .BR size[.{soft|hard|unchecked}]=<integer> ,
1195 is the maximum number of entries slapd will return answering a search
1197 If no size limit is explicitly requested by the client, the
1199 limit is used; if the requested size limit exceeds the
1202 .\".I "Administrative limit exceeded"
1203 .\"error is returned.
1204 limit, the value of the limit is used instead.
1207 limit is set to the keyword
1209 the soft limit is used in either case; if it is set to the keyword
1211 no hard limit is enforced.
1212 Explicit requests for size limits smaller or equal to the
1217 specifier sets a limit on the number of candidates a search request is allowed
1219 The rationale behind it is that searches for non-properly indexed
1220 attributes may result in large sets of candidates, which must be
1223 to determine whether they match the search filter or not.
1226 limit provides a means to drop such operations before they are even
1228 If the selected candidates exceed the
1230 limit, the search will abort with
1231 .IR "Unwilling to perform" .
1232 If it is set to the keyword
1234 no limit is applied (the default).
1237 the search is not even performed; this can be used to disallow searches
1238 for a specific set of users.
1239 If no limit specifier is set, the value is assigned to the
1245 to preserve the original behavior.
1247 In case of no match, the global limits are used.
1248 The default values are the same of
1257 control is requested, the
1259 size limit is used by default, because the request of a specific page size
1260 is considered an explicit request for a limitation on the number
1261 of entries to be returned.
1262 However, the size limit applies to the total count of entries returned within
1263 the search, and not to a single page.
1264 Additional size limits may be enforced; the syntax is
1265 .BR size.pr={<integer>|noEstimate|unlimited} ,
1268 is the max page size if no explicit limit is set; the keyword
1270 inhibits the server from returning an estimate of the total number
1271 of entries that might be returned
1272 (note: the current implementation does not return any estimate).
1275 indicates that no limit is applied to the pagedResults control page size.
1277 .B size.prtotal={<integer>|unlimited|disabled}
1278 allows to set a limit on the total number of entries that a pagedResults
1279 control allows to return.
1280 By default it is set to the
1285 is the max number of entries that the whole search with pagedResults control
1289 to allow unlimited number of entries to be returned, e.g. to allow
1290 the use of the pagedResults control as a means to circumvent size
1291 limitations on regular searches; the keyword
1293 disables the control, i.e. no paged results can be returned.
1294 Note that the total number of entries returned when the pagedResults control
1295 is requested cannot exceed the
1297 size limit of regular searches unless extended by the
1302 .B maxderefdepth <depth>
1303 Specifies the maximum number of aliases to dereference when trying to
1304 resolve an entry, used to avoid infinite alias loops. The default is 1.
1306 .B overlay <overlay-name>
1307 Add the specified overlay to this database. An overlay is a piece of
1308 code that intercepts database operations in order to extend or change
1309 them. Overlays are pushed onto
1310 a stack over the database, and so they will execute in the reverse
1311 of the order in which they were configured and the database itself
1312 will receive control last of all. Note that all of the database's
1313 regular settings should be configured before any overlay settings.
1315 .B readonly on | off
1316 This option puts the database into "read-only" mode. Any attempts to
1317 modify the database will return an "unwilling to perform" error. By
1318 default, readonly is off.
1321 .B replica uri=ldap[s]://<hostname>[:port]|host=<hostname>[:port]
1322 .B [starttls=yes|critical]
1323 .B [suffix=<suffix> [...]]
1324 .B bindmethod=simple|sasl [binddn=<simple DN>] [credentials=<simple password>]
1325 .B [saslmech=<SASL mech>] [secprops=<properties>] [realm=<realm>]
1326 .B [authcId=<authentication ID>] [authzId=<authorization ID>]
1327 .B [attr[!]=<attr list>]
1329 Specify a replication site for this database. Refer to the "OpenLDAP
1330 Administrator's Guide" for detailed information on setting up a replicated
1332 directory service. Zero or more
1334 instances can be used to select the subtrees that will be replicated
1335 (defaults to all the database).
1337 is deprecated in favor of the
1341 allows the replica LDAP server to be specified as an LDAP URI.
1346 requires the options
1350 and should only be used when adequate security services
1351 (e.g TLS or IPSEC) are in place. A
1357 Specific security properties (as with the
1359 keyword above) for a SASL bind can be set with the
1361 option. A non-default SASL realm can be set with the
1366 will use Kerberos, a kerberos instance should be given in
1370 can be given after the
1372 keyword to allow the selective replication of the listed attributes only;
1375 mark is used, the list is considered exclusive, i.e. the listed attributes
1377 If an objectClass is listed, all the related attributes
1378 are (are not) replicated.
1381 .B replogfile <filename>
1382 Specify the name of the replication log file to log changes to.
1383 The replication log is typically written by
1388 .BR slapd.replog (5)
1389 for more information. The specified file should be located
1390 in a directory with limited read/write/execute access as the replication
1391 logs may contain sensitive information.
1393 .B restrict <oplist>
1394 Specify a whitespace separated list of operations that are restricted.
1395 If defined inside a database specification, restrictions apply only
1396 to that database, otherwise they are global.
1397 Operations can be any of
1402 .BR extended[=<OID>] ,
1406 or the special pseudo-operations
1410 which respectively summarize read and write operations.
1418 keyword allows to indicate the OID of the specific operation
1422 Specify the distinguished name that is not subject to access control
1423 or administrative limit restrictions for operations on this database.
1424 This DN may or may not be associated with an entry. An empty root
1425 DN (the default) specifies no root access is to be granted. It is
1426 recommended that the rootdn only be specified when needed (such as
1427 when initially populating a database). If the rootdn is within
1428 a namingContext (suffix) of the database, a simple bind password
1429 may also be provided using the
1431 directive. Note that the rootdn is always needed when using syncrepl.
1433 .B rootpw <password>
1434 Specify a password (or hash of the password) for the rootdn. The
1435 password can only be set if the rootdn is within the namingContext
1436 (suffix) of the database.
1437 This option accepts all RFC 2307 userPassword formats known to
1440 description) as well as cleartext.
1442 may be used to generate a hash of a password. Cleartext
1443 and \fB{CRYPT}\fP passwords are not recommended. If empty
1444 (the default), authentication of the root DN is by other means
1445 (e.g. SASL). Use of SASL is encouraged.
1447 .B suffix <dn suffix>
1448 Specify the DN suffix of queries that will be passed to this
1449 backend database. Multiple suffix lines can be given and at least one is
1450 required for each database definition.
1451 If the suffix of one database is "inside" that of another, the database
1452 with the inner suffix must come first in the configuration file.
1454 .B subordinate [advertise]
1455 Specify that the current backend database is a subordinate of another
1456 backend database. A subordinate database may have only one suffix. This
1457 option may be used to glue multiple databases into a single namingContext.
1458 If the suffix of the current database is within the namingContext of a
1459 superior database, searches against the superior database will be
1460 propagated to the subordinate as well. All of the databases
1461 associated with a single namingContext should have identical rootdns.
1462 Behavior of other LDAP operations is unaffected by this setting. In
1463 particular, it is not possible to use moddn to move an entry from
1464 one subordinate to another subordinate within the namingContext.
1466 If the optional \fBadvertise\fP flag is supplied, the naming context of
1467 this database is advertised in the root DSE. The default is to hide this
1468 database context, so that only the superior context is visible.
1475 are used on the superior database, any glued subordinates that support
1476 these tools are opened as well.
1478 Databases that are glued together should usually be configured with the
1479 same indices (assuming they support indexing), even for attributes that
1480 only exist in some of these databases. In general, all of the glued
1481 databases should be configured as similarly as possible, since the intent
1482 is to provide the appearance of a single directory.
1484 Note that the \fIsubordinate\fP functionality is implemented internally
1485 by the \fIglue\fP overlay and as such its behavior will interact with other
1486 overlays in use. By default, the glue overlay is automatically configured as
1487 the last overlay on the superior backend. Its position on the backend
1488 can be explicitly configured by setting an \fBoverlay glue\fP directive
1489 at the desired position. This explicit configuration is necessary e.g.
1490 when using the \fIsyncprov\fP overlay, which needs to follow \fIglue\fP
1491 in order to work over all of the glued databases. E.g.
1495 suffix dc=example,dc=com
1503 .B syncrepl rid=<replica ID>
1504 .B provider=ldap[s]://<hostname>[:port]
1505 .B [type=refreshOnly|refreshAndPersist]
1506 .B [interval=dd:hh:mm:ss]
1507 .B [retry=[<retry interval> <# of retries>]+]
1508 .B searchbase=<base DN>
1509 .B [filter=<filter str>]
1510 .B [scope=sub|one|base]
1511 .B [attrs=<attr list>]
1513 .B [sizelimit=<limit>]
1514 .B [timelimit=<limit>]
1515 .B [schemachecking=on|off]
1516 .B [starttls=yes|critical]
1517 .B [bindmethod=simple|sasl]
1519 .B [saslmech=<mech>]
1520 .B [authcid=<identity>]
1521 .B [authzid=<identity>]
1522 .B [credentials=<passwd>]
1524 .B [secprops=<properties>]
1525 .B [logbase=<base DN>]
1526 .B [logfilter=<filter str>]
1527 .B [syncdata=default|accesslog|changelog]
1529 Specify the current database as a replica which is kept up-to-date with the
1530 master content by establishing the current
1532 as a replication consumer site running a
1535 The replica content is kept synchronized to the master content using
1536 the LDAP Content Synchronization protocol. Refer to the
1537 "OpenLDAP Administrator's Guide" for detailed information on
1538 setting up a replicated
1540 directory service using the
1544 identifies the current
1546 directive within the replication consumer site.
1547 It is a non-negative integer having no more than three digits.
1549 specifies the replication provider site containing the master content
1550 as an LDAP URI. If <port> is not given, the standard LDAP port number
1551 (389 or 636) is used. The content of the
1553 replica is defined using a search
1554 specification as its result set. The consumer
1556 will send search requests to the provider
1558 according to the search specification. The search specification includes
1559 .B searchbase, scope, filter, attrs, attrsonly, sizelimit,
1562 parameters as in the normal search specification.
1563 The \fBscope\fP defaults to \fBsub\fP, the \fBfilter\fP defaults to
1564 \fB(objectclass=*)\fP, and there is no default \fBsearchbase\fP. The
1565 \fBattrs\fP list defaults to \fB"*,+"\fP to return all user and operational
1566 attributes, and \fBattrsonly\fP is unset by default.
1567 The \fBsizelimit\fP and \fBtimelimit\fP only
1568 accept "unlimited" and positive integers, and both default to "unlimited".
1569 The LDAP Content Synchronization protocol has two operation types.
1572 operation, the next synchronization search operation
1573 is periodically rescheduled at an interval time (specified by
1575 parameter; 1 day by default)
1576 after each synchronization operation finishes.
1578 .B refreshAndPersist
1579 operation, a synchronization search remains persistent in the provider slapd.
1580 Further updates to the master replica will generate
1581 .B searchResultEntry
1582 to the consumer slapd as the search responses to the persistent
1583 synchronization search.
1584 If an error occurs during replication, the consumer will attempt to
1585 reconnect according to the
1587 parameter which is a list of the <retry interval> and <# of retries> pairs.
1588 For example, retry="60 10 300 3" lets the consumer retry every 60 seconds
1589 for the first 10 times and then retry every 300 seconds for the next 3
1590 times before stop retrying. The `+' in <# of retries> means indefinite
1591 number of retries until success.
1592 The schema checking can be enforced at the LDAP Sync
1593 consumer site by turning on the
1595 parameter. The default is off.
1598 parameter specifies use of the StartTLS extended operation
1599 to establish a TLS session before Binding to the provider. If the
1600 StartTLS request fails and the
1602 argument was used, the session will be aborted. Otherwise the syncrepl
1603 session continues without TLS.
1608 requires the options
1612 and should only be used when adequate security services
1613 (e.g. TLS or IPSEC) are in place.
1614 .B REMEMBER: simple bind credentials must be in cleartext!
1621 Depending on the mechanism, an authentication identity and/or
1622 credentials can be specified using
1628 parameter may be used to specify an authorization identity.
1629 Specific security properties (as with the
1631 keyword above) for a SASL bind can be set with the
1633 option. A non default SASL realm can be set with the
1637 Rather than replicating whole entries, the consumer can query logs of
1638 data modifications. This mode of operation is referred to as \fIdelta
1639 syncrepl\fP. In addition to the above parameters, the
1643 parameters must be set appropriately for the log that will be used. The
1645 parameter must be set to either "accesslog" if the log conforms to the
1646 .BR slapo-accesslog (5)
1647 log format, or "changelog" if the log conforms
1648 to the obsolete \fIchangelog\fP format. If the
1650 parameter is omitted or set to "default" then the log parameters are
1655 This option is only applicable in a slave
1656 database updated using
1658 It specifies the DN permitted to update (subject to access controls)
1659 the replica (typically, this is the DN
1661 binds to update the replica). Generally, this DN
1668 Specify the referral to pass back when
1670 is asked to modify a replicated local database.
1671 If specified multiple times, each url is provided.
1673 .SH DATABASE-SPECIFIC OPTIONS
1674 Each database may allow specific configuration options; they are
1675 documented separately in the backends' manual pages.
1677 The following backends can be compiled into slapd.
1678 They are documented in the
1679 .BR slapd-<backend> (5)
1683 This is the recommended primary backend for a normal slapd database.
1684 It takes care to configure it properly.
1685 It uses the transactional database interface of the Sleepycat Berkeley
1686 DB (BDB) package to store data.
1689 This backend is used to manage the configuration of slapd run-time.
1692 This backend is experimental.
1693 It serves up referrals based upon SRV resource records held in the
1697 This is a variant of the BDB backend that uses a hierarchical database
1698 layout which supports subtree renames.
1701 This backend acts as a proxy to forward incoming requests to another
1705 This is an easy-to-configure but obsolete database backend. It
1706 does not offer the data durability features of the BDB and HDB
1707 backends and hence is deprecated in favor of these robust backends.
1708 LDBM uses lightweight non-transactional DB interfaces,
1709 such as those providing by GDBM or Berkeley DB, to store data.
1712 This database uses the filesystem to build the tree structure
1713 of the database, using plain ascii files to store data.
1714 Its usage should be limited to very simple databases, where performance
1715 is not a requirement.
1718 This backend performs basic LDAP proxying with respect to a set of
1719 remote LDAP servers. It is an enhancement of the ldap backend.
1722 This backend provides information about the running status of the slapd
1726 Operations in this backend succeed but do nothing.
1729 This backend is provided for demonstration purposes only.
1730 It serves up user account information from the system
1735 This backend embeds a
1737 interpreter into slapd.
1738 It runs Perl subroutines to implement LDAP operations.
1741 This backend is experimental.
1742 It redirects LDAP operations to another database
1743 in the same server, based on the naming context of the request.
1744 Its use requires the
1748 for details) to rewrite the naming context of the request.
1749 It is primarily intended to implement virtual views on databases
1750 that actually store data.
1753 This backend executes external programs to implement LDAP operations.
1754 It is primarily intended to be used in prototypes.
1757 This backend is experimental.
1758 It services LDAP requests from an SQL database.
1760 The following overlays can be compiled into slapd.
1761 They are documented in the
1762 .BR slapo-<overlay> (5)
1767 This overlay can record accesses to a given backend database on another
1772 This overlay records changes on a given backend database to an LDIF log
1774 By default it is not built.
1778 This overlay allows automatic referral chasing when a referral would
1779 have been returned, either when configured by the server or when
1780 requested by the client.
1784 This overlay allows selected operations to be denied, similar to the
1785 \fBrestrict\fP option.
1789 This is a demo overlay which extends the Compare operation to detect
1790 members of a dynamic group.
1791 It has no effect on any other operations.
1795 This overlay allows expansion of dynamic groups and more.
1799 This overlay maintains a service entry in the database with the DN,
1800 modification type, modifiersName and modifyTimestamp of the last write
1801 operation performed on that database.
1805 This overlay allows caching of LDAP search requests in a local database.
1806 It is most often used with the ldap or meta backends.
1810 This overlay provides a variety of password control mechanisms,
1811 e.g. password aging, password reuse and duplication control, mandatory
1812 password resets, etc.
1815 Referential Integrity.
1816 This overlay can be used with a backend database such as
1818 to maintain the cohesiveness of a schema which utilizes reference
1823 This overlay is useful to test the behavior of clients when
1824 server-generated erroneous and/or unusual responses occur.
1828 This overlay is experimental.
1829 It performs basic DN/data rewrite and
1830 objectClass/attributeType mapping.
1834 This overlay implements the provider-side support for
1836 replication, including persistent search functionality.
1840 This overlay can be used with a backend database such as
1842 to create a "translucent proxy".
1843 Content of entries retrieved from a remote LDAP server can be partially
1844 overridden by the database.
1847 Attribute Uniqueness.
1848 This overlay can be used with a backend database such as
1850 to enforce the uniqueness of some or all attributes within a subtree.
1853 Here is a short example of a configuration file:
1857 include SYSCONFDIR/schema/core.schema
1858 pidfile LOCALSTATEDIR/slapd.pid
1860 # Subtypes of "name" (e.g. "cn" and "ou") with the
1861 # option ";x-hidden" can be searched for/compared,
1862 # but are not shown. See \fBslapd.access\fP(5).
1863 attributeoptions x-hidden lang-
1864 access to attr=name;x-hidden by * =cs
1866 # Protect passwords. See \fBslapd.access\fP(5).
1867 access to attrs=userPassword by * auth
1868 # Read access to other attributes and entries.
1869 access to * by * read
1872 suffix "dc=our-domain,dc=com"
1873 # The database directory MUST exist prior to
1874 # running slapd AND should only be accessible
1875 # by the slapd/tools. Mode 0700 recommended.
1876 directory LOCALSTATEDIR/openldap-data
1877 # Indices to maintain
1878 index objectClass eq
1879 index cn,sn,mail pres,eq,approx,sub
1881 # We serve small clients that do not handle referrals,
1882 # so handle remote lookups on their behalf.
1885 uri ldap://ldap.some-server.com/
1890 "OpenLDAP Administrator's Guide" contains a longer annotated
1891 example of a configuration file.
1892 The original ETCDIR/slapd.conf is another example.
1896 default slapd configuration file
1900 .BR slapd\-dnssrv (5),
1902 .BR slapd\-ldap (5),
1903 .BR slapd\-ldbm (5),
1904 .BR slapd\-ldif (5),
1905 .BR slapd\-meta (5),
1906 .BR slapd\-monitor (5),
1907 .BR slapd\-null (5),
1908 .BR slapd\-passwd (5),
1909 .BR slapd\-perl (5),
1910 .BR slapd\-relay (5),
1911 .BR slapd\-shell (5),
1913 .BR slapd.access (5),
1914 .BR slapd.plugin (5),
1915 .BR slapd.replog (5),
1927 Known overlays are documented in
1928 .BR slapo\-accesslog (5),
1929 .BR slapo\-auditlog (5),
1930 .BR slapo\-chain (5),
1931 .BR slapo\-dynlist (5),
1932 .BR slapo\-lastmod (5),
1933 .BR slapo\-pcache (5),
1934 .BR slapo\-ppolicy (5),
1935 .BR slapo\-refint (5),
1936 .BR slapo\-retcode (5),
1938 .BR slapo\-syncprov (5),
1939 .BR slapo\-translucent (5),
1940 .BR slapo\-unique (5).
1942 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
1943 .SH ACKNOWLEDGEMENTS
1945 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
1947 is derived from University of Michigan LDAP 3.3 Release.
projects / openldap / blob