1 .TH SLAPD.CONF 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2008 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 SLAPD tools
26 file consists of a series of global configuration options that apply to
28 as a whole (including all backends), followed by zero or more database
29 backend definitions that contain information specific to a backend
31 The configuration options are case-insensitive;
32 their value, on a case by case basis, may be case-sensitive.
39 # comment - these options apply to every database
40 <global configuration options>
41 # first database definition & configuration options
42 database <backend 1 type>
43 <configuration options specific to backend 1>
44 # subsequent database definitions & configuration options
48 As many backend-specific sections as desired may be included. Global
49 options can be overridden in a backend (for options that appear more
50 than once, the last appearance in the
54 If a line begins with white space, it is considered a continuation
55 of the previous line. No physical line should be over 2000 bytes
58 Blank lines and comment lines beginning with
59 a `#' character are ignored. Note: continuation lines are unwrapped
60 before comment processing is applied.
62 Arguments on configuration lines are separated by white space. If an
63 argument contains white space, the argument should be enclosed in
64 double quotes. If an argument contains a double quote (`"') or a
65 backslash character (`\\'), the character should be preceded by a
68 The specific configuration options available are discussed below in the
69 Global Configuration Options, General Backend Options, and General Database
70 Options. Backend-specific options are discussed in the
72 manual pages. Refer to the "OpenLDAP Administrator's Guide" for more
73 details on the slapd configuration file.
74 .SH GLOBAL CONFIGURATION OPTIONS
75 Options described in this section apply to all backends, unless specifically
76 overridden in a backend definition. Arguments that should be replaced by
77 actual text are shown in brackets <>.
79 .B access to <what> "[ by <who> <access> <control> ]+"
80 Grant access (specified by <access>) to a set of entries and/or
81 attributes (specified by <what>) by one or more requestors (specified
83 If no access controls are present, the default policy
84 allows anyone and everyone to read anything but restricts
85 updates to rootdn. (e.g., "access to * by * read").
86 The rootdn can always read and write EVERYTHING!
89 and the "OpenLDAP's Administrator's Guide" for details.
92 Specify a set of features (separated by white space) to
95 allows acceptance of LDAPv2 bind requests. Note that
97 does not truly implement LDAPv2 (RFC 1777), now Historic (RFC 3494).
99 allows anonymous bind when credentials are not empty (e.g.
102 allows unauthenticated (anonymous) bind when DN is not empty.
104 allows unauthenticated (anonymous) update operations to be processed
105 (subject to access controls and other administrative limits).
107 allows unauthenticated (anonymous) proxy authorization control to be processed
108 (subject to access controls, authorization and other administrative limits).
110 .B argsfile <filename>
111 The ( absolute ) name of a file that will hold the
113 server's command line options
114 if started without the debugging command line option.
116 .B attributeoptions [option-name]...
117 Define tagging attribute options or option tag/range prefixes.
118 Options must not end with `-', prefixes must end with `-'.
119 The `lang-' prefix is predefined.
122 directive, `lang-' will no longer be defined and you must specify it
123 explicitly if you want it defined.
125 An attribute description with a tagging option is a subtype of that
126 attribute description without the option.
127 Except for that, options defined this way have no special semantics.
128 Prefixes defined this way work like the `lang-' options:
129 They define a prefix for tagging options starting with the prefix.
130 That is, if you define the prefix `x-foo-', you can use the option
132 Furthermore, in a search or compare, a prefix or range name (with
133 a trailing `-') matches all options starting with that name, as well
134 as the option with the range name sans the trailing `-'.
135 That is, `x-foo-bar-' matches `x-foo-bar' and `x-foo-bar-baz'.
137 RFC 4520 reserves options beginning with `x-' for private experiments.
138 Other options should be registered with IANA, see RFC 4520 section 3.5.
139 OpenLDAP also has the `binary' option built in, but this is a transfer
140 option, not a tagging option.
143 .B attributetype "(\ <oid>\
145 [DESC\ <description>]\
154 [NO\-USER\-MODIFICATION]\
155 [USAGE\ <attributeUsage>]\ )"
157 Specify an attribute type using the LDAPv3 syntax defined in RFC 4512.
158 The slapd parser extends the RFC 4512 definition by allowing string
159 forms as well as numeric OIDs to be used for the attribute OID and
160 attribute syntax OID.
166 .B authz-policy <policy>
167 Used to specify which rules to use for Proxy Authorization. Proxy
168 authorization allows a client to authenticate to the server using one
169 user's credentials, but specify a different identity to use for authorization
170 and access control purposes. It essentially allows user A to login as user
171 B, using user A's password.
174 flag disables proxy authorization. This is the default setting.
177 flag will use rules in the
179 attribute of the authorization DN.
182 flag will use rules in the
184 attribute of the authentication DN.
187 flag, an alias for the deprecated value of
189 will allow any of the above, whatever succeeds first (checked in
195 flag requires both authorizations to succeed.
198 The rules are mechanisms to specify which identities are allowed
199 to perform proxy authorization.
202 attribute in an entry specifies which other users
203 are allowed to proxy login to this entry. The
206 an entry specifies which other users this user can authorize as. Use of
209 abused if users are allowed to write arbitrary values to this attribute.
212 attribute must be protected with ACLs such that
213 only privileged users can modify it.
220 or a set of identities; it can take five forms:
223 .B ldap:///<base>??[<scope>]?<filter>
226 .B dn[.<dnstyle>]:<pattern>
229 .B u[.<mech>[/<realm>]]:<pattern>
232 .B group[/objectClass[/attributeType]]:<pattern>
239 .B <dnstyle>:={exact|onelevel|children|subtree|regex}
242 The first form is a valid LDAP
250 portions must be absent, so that the search occurs locally on either
256 with the optional style modifiers
262 for exact, onelevel, children and subtree matches, which cause
264 to be normalized according to the DN normalization rules, or the special
266 style, which causes the
268 to be treated as a POSIX (''extended'') regular expression, as
275 means any non-anonymous DN.
276 The third form is a SASL
278 with the optional fields
282 that allow to specify a SASL
284 and eventually a SASL
286 for those mechanisms that support one.
287 The need to allow the specification of a mechanism is still debated,
288 and users are strongly discouraged to rely on this possibility.
289 The fourth form is a group specification, consisting of the keyword
291 optionally followed by the specification of the group
297 is searched with base scope, and in case of match, the values of the
300 are searched for the asserted DN.
301 For backwards compatibility, if no identity type is provided, i.e. only
305 is assumed; as a consequence,
307 is subjected to DN normalization.
308 Since the interpretation of
312 can impact security, users are strongly encouraged
313 to explicitly set the type of identity specification that is being used.
314 A subset of these rules can be used as third arg in the
316 statement (see below); significantly, the
318 provided it results in exactly one entry,
324 .B authz-regexp <match> <replace>
325 Used by the authentication framework to convert simple user names,
326 such as provided by SASL subsystem, or extracted from certificates
327 in case of cert-based SASL EXTERNAL, or provided within the RFC 4370
328 "proxied authorization" control, to an LDAP DN used for
329 authorization purposes. Note that the resulting DN need not refer
330 to an existing entry to be considered valid. When an authorization
331 request is received from the SASL subsystem, the SASL
336 are taken, when available, and combined into a name of the form
340 .B UID=<username>[[,CN=<realm>],CN=<mechanism>],CN=auth
343 This name is then compared against the
345 POSIX (''extended'') regular expression, and if the match is successful,
346 the name is replaced with the
348 string. If there are wildcard strings in the
350 regular expression that are enclosed in parenthesis, e.g.
356 then the portion of the name that matched the wildcard will be stored
357 in the numbered placeholder variable $1. If there are other wildcard strings
358 in parenthesis, the matching strings will be in $2, $3, etc. up to $9. The
359 placeholders can then be used in the
364 .B UID=$1,OU=Accounts,DC=example,DC=com
367 The replaced name can be either a DN, i.e. a string prefixed by "dn:",
369 If the latter, the server will use the URI to search its own database(s)
370 and, if the search returns exactly one entry, the name is
371 replaced by the DN of that entry. The LDAP URI must have no
372 hostport, attrs, or extensions components, but the filter is mandatory,
376 .B ldap:///OU=Accounts,DC=example,DC=com??one?(UID=$1)
379 The protocol portion of the URI must be strictly
381 Note that this search is subject to access controls. Specifically,
382 the authentication identity must have "auth" access in the subject.
386 options can be given in the configuration file to allow for multiple matching
387 and replacement patterns. The matching patterns are checked in the order they
388 appear in the file, stopping at the first successful match.
391 .\"Because the plus sign + is a character recognized by the regular expression engine,
392 .\"and it will appear in names that include a REALM, be careful to escape the
393 .\"plus sign with a backslash \\+ to remove the character's special meaning.
396 .B concurrency <integer>
397 Specify a desired level of concurrency. Provided to the underlying
398 thread system as a hint. The default is not to provide any hint.
400 .B conn_max_pending <integer>
401 Specify the maximum number of pending requests for an anonymous session.
402 If requests are submitted faster than the server can process them, they
403 will be queued up to this limit. If the limit is exceeded, the session
404 is closed. The default is 100.
406 .B conn_max_pending_auth <integer>
407 Specify the maximum number of pending requests for an authenticated session.
410 .B defaultsearchbase <dn>
411 Specify a default search base to use when client submits a
412 non-base search request with an empty base DN.
413 Base scoped search requests with an empty base DN are not affected.
415 .B disallow <features>
416 Specify a set of features (separated by white space) to
417 disallow (default none).
419 disables acceptance of anonymous bind requests. Note that this setting
420 does not prohibit anonymous directory access (See "require authc").
422 disables simple (bind) authentication.
424 disables forcing session to anonymous status (see also
426 upon StartTLS operation receipt.
428 disallows the StartTLS operation if authenticated (see also
432 .B ditcontentrule "(\ <oid>\
434 [DESC\ <description>]\
441 Specify an DIT Content Rule using the LDAPv3 syntax defined in RFC 4512.
442 The slapd parser extends the RFC 4512 definition by allowing string
443 forms as well as numeric OIDs to be used for the attribute OID and
444 attribute syntax OID.
450 .B gentlehup { on | off }
451 A SIGHUP signal will only cause a 'gentle' shutdown-attempt:
453 will stop listening for new connections, but will not close the
454 connections to the current clients. Future write operations return
455 unwilling-to-perform, though. Slapd terminates when all clients
456 have closed their connections (if they ever do), or \- as before \-
457 if it receives a SIGTERM signal. This can be useful if you wish to
458 terminate the server and start a new
461 .B with another database,
462 without disrupting the currently active clients.
463 The default is off. You may wish to use
465 along with this option.
467 .B idletimeout <integer>
468 Specify the number of seconds to wait before forcibly closing
469 an idle client connection. A idletimeout of 0 disables this
470 feature. The default is 0.
472 .B include <filename>
473 Read additional configuration information from the given file before
474 continuing with the next line of the current file.
476 .B index_intlen <integer>
477 Specify the key length for ordered integer indices. The most significant
478 bytes of the binary integer will be used for index keys. The default
479 value is 4, which provides exact indexing for 31 bit values.
480 A floating point representation is used to index too large values.
482 .B index_substr_if_minlen <integer>
483 Specify the minimum length for subinitial and subfinal indices. An
484 attribute value must have at least this many characters in order to be
485 processed by the indexing functions. The default is 2.
487 .B index_substr_if_maxlen <integer>
488 Specify the maximum length for subinitial and subfinal indices. Only
489 this many characters of an attribute value will be processed by the
490 indexing functions; any excess characters are ignored. The default is 4.
492 .B index_substr_any_len <integer>
493 Specify the length used for subany indices. An attribute value must have
494 at least this many characters in order to be processed. Attribute values
495 longer than this length will be processed in segments of this length. The
496 default is 4. The subany index will also be used in subinitial and
497 subfinal index lookups when the filter string is longer than the
498 .I index_substr_if_maxlen
501 .B index_substr_any_step <integer>
502 Specify the steps used in subany index lookups. This value sets the offset
503 for the segments of a filter string that are processed for a subany index
504 lookup. The default is 2. For example, with the default values, a search
505 using this filter "cn=*abcdefgh*" would generate index lookups for
506 "abcd", "cdef", and "efgh".
509 Note: Indexing support depends on the particular backend in use. Also,
510 changing these settings will generally require deleting any indices that
511 depend on these parameters and recreating them with
516 .B ldapsyntax "(\ <oid>\
517 [DESC\ <description>]\
518 [X-SUBST <substitute\-syntax>]\ )"
520 Specify an LDAP syntax using the LDAPv3 syntax defined in RFC 4512.
521 The slapd parser extends the RFC 4512 definition by allowing string
522 forms as well as numeric OIDs to be used for the syntax OID.
526 The slapd parser also honors the
528 extension (an OpenLDAP-specific extension), which allows to use the
530 statement to define a non-implemented syntax along with another syntax,
532 .IR substitute\-syntax ,
533 as its temporary replacement.
535 .I substitute\-syntax
537 This allows to define attribute types that make use of non-implemented syntaxes
538 using the correct syntax OID.
541 is used, this configuration statement would result in an error,
542 since no handlers would be associated to the resulting syntax structure.
547 Specifies the Security Strength Factor (SSF) to be given local LDAP sessions,
548 such as those to the ldapi:// listener. For a description of SSF values,
552 option description. The default is 71.
554 .B logfile <filename>
555 Specify a file for recording debug log messages. By default these messages
556 only go to stderr and are not recorded anywhere else. Specifying a logfile
557 copies messages to both stderr and the logfile.
559 .B loglevel <integer> [...]
560 Specify the level at which debugging statements and operation
561 statistics should be syslogged (currently logged to the
563 LOG_LOCAL4 facility).
564 They must be considered subsystems rather than increasingly verbose
566 Some messages with higher priority are logged regardless
567 of the configured loglevel as soon as any logging is configured.
568 Log levels are additive, and available levels are:
579 debug packet handling
583 heavy trace debugging (function args)
587 connection management
591 print out packets sent and received
595 search filter processing
599 configuration file processing
603 access control list processing
607 connections, LDAP operations, results (recommended)
611 stats log entries sent
615 print communication with shell backends
627 \"data indexing (unused)
635 only messages that get logged whatever log level is set
638 The desired log level can be input as a single integer that combines
639 the (ORed) desired levels, both in decimal or in hexadecimal notation,
640 as a list of integers (that are ORed internally),
641 or as a list of the names that are shown between brackets, such that
654 can be used as a shortcut to enable logging at all levels (equivalent to -1).
657 or the equivalent integer representation, causes those messages
658 that are logged regardless of the configured loglevel to be logged.
659 In fact, if loglevel is set to 0, no logging occurs,
662 level is required to have high priority messages logged.
664 The loglevel defaults to \fBstats\fP.
665 This level should usually also be included when using other loglevels, to
666 help analyze the logs.
669 .B moduleload <filename>
670 Specify the name of a dynamically loadable module to load. The filename
671 may be an absolute path name or a simple filename. Non-absolute names
672 are searched for in the directories specified by the
674 option. This option and the
676 option are only usable if slapd was compiled with --enable-modules.
678 .B modulepath <pathspec>
679 Specify a list of directories to search for loadable modules. Typically
680 the path is colon-separated but this depends on the operating system.
683 .B objectclass "(\ <oid>\
685 [DESC\ <description>]\
688 [{ ABSTRACT | STRUCTURAL | AUXILIARY }]\
689 [MUST\ <oids>] [MAY\ <oids>] )"
691 Specify an objectclass using the LDAPv3 syntax defined in RFC 4512.
692 The slapd parser extends the RFC 4512 definition by allowing string
693 forms as well as numeric OIDs to be used for the object class OID.
697 description.) Object classes are "STRUCTURAL" by default.
700 .B objectidentifier <name> "{ <oid> | <name>[:<suffix>] }"
701 Define a string name that equates to the given OID. The string can be used
702 in place of the numeric OID in objectclass and attribute definitions. The
703 name can also be used with a suffix of the form ":xx" in which case the
704 value "oid.xx" will be used.
706 .B password-hash <hash> [<hash>...]
707 This option configures one or more hashes to be used in generation of user
708 passwords stored in the userPassword attribute during processing of
709 LDAP Password Modify Extended Operations (RFC 3062).
710 The <hash> must be one of
724 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
729 use the MD5 algorithm (RFC 1321), the latter with a seed.
736 indicates that the new password should be
737 added to userPassword as clear text.
739 Note that this option does not alter the normal user applications
740 handling of userPassword during LDAP Add, Modify, or other LDAP operations.
742 .B password\-crypt\-salt\-format <format>
743 Specify the format of the salt passed to
745 when generating {CRYPT} passwords (see
747 during processing of LDAP Password Modify Extended Operations (RFC 3062).
749 This string needs to be in
751 format and may include one (and only one) %s conversion.
752 This conversion will be substituted with a string of random
753 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
754 provides a two character salt and "$1$%.8s" tells some
755 versions of crypt(3) to use an MD5 algorithm and provides
756 8 random characters of salt. The default is "%s", which
757 provides 31 characters of salt.
759 .B pidfile <filename>
760 The ( absolute ) name of a file that will hold the
762 server's process ID ( see
764 ) if started without the debugging command line option.
767 Specify the referral to pass back when
769 cannot find a local database to handle a request.
770 If specified multiple times, each url is provided.
772 .B require <conditions>
773 Specify a set of conditions (separated by white space) to
774 require (default none).
775 The directive may be specified globally and/or per-database;
776 databases inherit global conditions, so per-database specifications
779 requires bind operation prior to directory operations.
781 requires session to be using LDAP version 3.
783 requires authentication prior to directory operations.
785 requires SASL authentication prior to directory operations.
787 requires strong authentication prior to directory operations.
788 The strong keyword allows protected "simple" authentication
789 as well as SASL authentication.
791 may be used to require no conditions (useful to clear out globally
792 set conditions within a particular database); it must occur first
793 in the list of conditions.
795 .B reverse-lookup on | off
796 Enable/disable client name unverified reverse lookup (default is
798 if compiled with --enable-rlookups).
801 Specify the name of an LDIF(5) file containing user defined attributes
802 for the root DSE. These attributes are returned in addition to the
803 attributes normally produced by slapd.
805 The root DSE is an entry with information about the server and its
806 capabilities, in operational attributes.
807 It has the empty DN, and can be read with e.g.:
809 ldapsearch -x -b "" -s base "+"
811 See RFC 4512 section 5.1 for details.
814 Used to specify the fully qualified domain name used for SASL processing.
816 .B sasl-realm <realm>
817 Specify SASL realm. Default is empty.
819 .B sasl-secprops <properties>
820 Used to specify Cyrus SASL security properties.
823 flag (without any other properties) causes the flag properties
824 default, "noanonymous,noplain", to be cleared.
827 flag disables mechanisms susceptible to simple passive attacks.
830 flag disables mechanisms susceptible to active attacks.
833 flag disables mechanisms susceptible to passive dictionary attacks.
836 flag disables mechanisms which support anonymous login.
839 flag require forward secrecy between sessions.
842 require mechanisms which pass client credentials (and allow
843 mechanisms which can pass credentials to do so).
846 property specifies the minimum acceptable
847 .I security strength factor
848 as an integer approximate to effective key length used for
849 encryption. 0 (zero) implies no protection, 1 implies integrity
850 protection only, 56 allows DES or other weak ciphers, 112
851 allows triple DES and other strong ciphers, 128 allows RC4,
852 Blowfish and other modern strong ciphers. The default is 0.
855 property specifies the maximum acceptable
856 .I security strength factor
857 as an integer (see minssf description). The default is INT_MAX.
860 property specifies the maximum security layer receive buffer
861 size allowed. 0 disables security layers. The default is 65536.
864 Specify the distinguished name for the subschema subentry that
865 controls the entries on this server. The default is "cn=Subschema".
867 .B security <factors>
868 Specify a set of security strength factors (separated by white space)
872 option for a description of security strength factors).
873 The directive may be specified globally and/or per-database.
875 specifies the overall security strength factor.
877 specifies the transport security strength factor.
879 specifies the TLS security strength factor.
881 specifies the SASL security strength factor.
883 specifies the overall security strength factor to require for
885 .B update_transport=<n>
886 specifies the transport security strength factor to require for
889 specifies the TLS security strength factor to require for
892 specifies the SASL security strength factor to require for
895 specifies the security strength factor required for
897 username/password authentication.
900 factor is measure of security provided by the underlying transport,
901 e.g. ldapi:// (and eventually IPSEC). It is not normally used.
903 .B serverID <integer> [<URL>]
904 Specify an integer ID from 0 to 4095 for this server (limited
905 to 3 hexadecimal digits).
907 required when using multimaster replication and each master must have a
908 unique ID. Note that this requirement also applies to separate masters
909 contributing to a glued set of databases.
910 If the URL is provided, this directive may be specified
911 multiple times, providing a complete list of participating servers
912 and their IDs. The fully qualified hostname of each server should be
913 used in the supplied URLs. The IDs are used in the "replica id" field
914 of all CSNs generated by the specified server. The default value is zero.
921 .B sizelimit {<integer>|unlimited}
923 .B sizelimit size[.{soft|hard|unchecked}]=<integer> [...]
924 Specify the maximum number of entries to return from a search operation.
925 The default size limit is 500.
928 to specify no limits.
929 The second format allows a fine grain setting of the size limits.
930 Extra args can be added on the same line.
933 for an explanation of the different flags.
935 .B sockbuf_max_incoming <integer>
936 Specify the maximum incoming LDAP PDU size for anonymous sessions.
937 The default is 262143.
939 .B sockbuf_max_incoming_auth <integer>
940 Specify the maximum incoming LDAP PDU size for authenticated sessions.
941 The default is 4194303.
943 .B sortvals <attr> [...]
944 Specify a list of multi-valued attributes whose values will always
945 be maintained in sorted order. Using this option will allow Modify,
946 Compare, and filter evaluations on these attributes to be performed
947 more efficiently. The resulting sort order depends on the
948 attributes' syntax and matching rules and may not correspond to
949 lexical order or any other recognizable order.
952 Specify the maximum size of the primary thread pool.
953 The default is 16; the minimum value is 2.
955 .B timelimit {<integer>|unlimited}
957 .B timelimit time[.{soft|hard}]=<integer> [...]
958 Specify the maximum number of seconds (in real time)
960 will spend answering a search request. The default time limit is 3600.
963 to specify no limits.
964 The second format allows a fine grain setting of the time limits.
965 Extra args can be added on the same line.
968 for an explanation of the different flags.
970 .B tool-threads <integer>
971 Specify the maximum number of threads to use in tool mode.
972 This should not be greater than the number of CPUs in the system.
974 .\"ucdata-path is obsolete / ignored...
976 .\".B ucdata-path <path>
977 .\"Specify the path to the directory containing the Unicode character
978 .\"tables. The default path is DATADIR/ucdata.
982 is built with support for Transport Layer Security, there are more options
985 .B TLSCipherSuite <cipher-suite-spec>
986 Permits configuring what ciphers will be accepted and the preference order.
987 <cipher-suite-spec> should be a cipher specification for OpenSSL. Example:
989 TLSCipherSuite HIGH:MEDIUM:+SSLv2
991 To check what ciphers a given spec selects, use:
994 openssl ciphers -v <cipher-suite-spec>
997 To obtain the list of ciphers in GNUtls use:
1004 .B TLSCACertificateFile <filename>
1005 Specifies the file that contains certificates for all of the Certificate
1010 .B TLSCACertificatePath <path>
1011 Specifies the path of a directory that contains Certificate Authority
1012 certificates in separate individual files. Usually only one of this
1013 or the TLSCACertificateFile is used. This directive is not supported
1016 .B TLSCertificateFile <filename>
1017 Specifies the file that contains the
1021 .B TLSCertificateKeyFile <filename>
1022 Specifies the file that contains the
1024 server private key that matches the certificate stored in the
1025 .B TLSCertificateFile
1026 file. Currently, the private key must not be protected with a password, so
1027 it is of critical importance that it is protected carefully.
1029 .B TLSDHParamFile <filename>
1030 This directive specifies the file that contains parameters for Diffie-Hellman
1031 ephemeral key exchange. This is required in order to use a DSA certificate on
1032 the server. If multiple sets of parameters are present in the file, all of
1033 them will be processed. Note that setting this option may also enable
1034 Anonymous Diffie-Hellman key exchanges in certain non-default cipher suites.
1035 You should append "!ADH" to your cipher suites if you have changed them
1036 from the default, otherwise no certificate exchanges or verification will
1037 be done. When using GNUtls these parameters are always generated randomly so
1038 this directive is ignored.
1040 .B TLSRandFile <filename>
1041 Specifies the file to obtain random bits from when /dev/[u]random
1042 is not available. Generally set to the name of the EGD/PRNGD socket.
1043 The environment variable RANDFILE can also be used to specify the filename.
1044 This directive is ignored with GNUtls.
1046 .B TLSVerifyClient <level>
1047 Specifies what checks to perform on client certificates in an
1048 incoming TLS session, if any.
1051 can be specified as one of the following keywords:
1055 This is the default.
1057 will not ask the client for a certificate.
1060 The client certificate is requested. If no certificate is provided,
1061 the session proceeds normally. If a bad certificate is provided,
1062 it will be ignored and the session proceeds normally.
1065 The client certificate is requested. If no certificate is provided,
1066 the session proceeds normally. If a bad certificate is provided,
1067 the session is immediately terminated.
1069 .B demand | hard | true
1070 These keywords are all equivalent, for compatibility reasons.
1071 The client certificate is requested. If no certificate is provided,
1072 or a bad certificate is provided, the session is immediately terminated.
1074 Note that a valid client certificate is required in order to use the
1075 SASL EXTERNAL authentication mechanism with a TLS session. As such,
1078 setting must be chosen to enable SASL EXTERNAL authentication.
1081 .B TLSCRLCheck <level>
1082 Specifies if the Certificate Revocation List (CRL) of the CA should be
1083 used to verify if the client certificates have not been revoked. This
1085 .B TLSCACertificatePath
1086 parameter to be set. This directive is ignored with GNUtls.
1088 can be specified as one of the following keywords:
1092 No CRL checks are performed
1095 Check the CRL of the peer certificate
1098 Check the CRL for a whole certificate chain
1101 .B TLSCRLFile <filename>
1102 Specifies a file containing a Certificate Revocation List to be used
1103 for verifying that certificates have not been revoked. This directive is
1104 only valid when using GNUtls.
1105 .SH GENERAL BACKEND OPTIONS
1106 Options in this section only apply to the configuration file section
1107 for the specified backend. They are supported by every
1110 .B backend <databasetype>
1111 Mark the beginning of a backend definition. <databasetype>
1128 depending on which backend will serve the database.
1130 .SH GENERAL DATABASE OPTIONS
1131 Options in this section only apply to the configuration file section
1132 for the database in which they are defined. They are supported by every
1133 type of backend. Note that the
1137 option are mandatory for each database.
1139 .B database <databasetype>
1140 Mark the beginning of a new database instance definition. <databasetype>
1157 depending on which backend will serve the database.
1160 Controls whether the database will be used to answer
1161 queries. A database that is hidden will never be
1162 selected to answer any queries, and any suffix configured
1163 on the database will be ignored in checks for conflicts
1164 with other databases. By default, hidden is off.
1169 will automatically maintain the
1170 modifiersName, modifyTimestamp, creatorsName, and
1171 createTimestamp attributes for entries. It also controls
1172 the entryCSN and entryUUID attributes, which are needed
1173 by the syncrepl provider. By default, lastmod is on.
1175 .B limits <who> <limit> [<limit> [...]]
1176 Specify time and size limits based on who initiated an operation.
1183 anonymous | users | [dn[.<style>]=]<pattern> | group[/oc[/at]]=<pattern>
1189 <style> ::= exact | base | onelevel | subtree | children | regex | anonymous
1194 matches all unauthenticated clients.
1197 matches all authenticated clients;
1200 dn pattern is assumed unless otherwise specified by qualifying
1201 the (optional) key string
1207 (which are synonyms), to require an exact match; with
1209 to require exactly one level of depth match; with
1211 to allow any level of depth match, including the exact match; with
1213 to allow any level of depth match, not including the exact match;
1215 explicitly requires the (default) match based on POSIX (''extended'')
1216 regular expression pattern.
1219 matches unbound operations; the
1222 The same behavior is obtained by using the
1229 with the optional objectClass
1235 sets the limits for any DN listed in the values of the
1241 group objectClass (default
1243 whose DN exactly matches
1246 The currently supported limits are
1251 The syntax for time limits is
1252 .BR time[.{soft|hard}]=<integer> ,
1255 is the number of seconds slapd will spend answering a search request.
1256 If no time limit is explicitly requested by the client, the
1258 limit is used; if the requested time limit exceeds the
1261 .\".I "Administrative limit exceeded"
1262 .\"error is returned.
1263 limit, the value of the limit is used instead.
1266 limit is set to the keyword
1268 the soft limit is used in either case; if it is set to the keyword
1270 no hard limit is enforced.
1271 Explicit requests for time limits smaller or equal to the
1274 If no limit specifier is set, the value is assigned to the
1280 to preserve the original behavior.
1282 The syntax for size limits is
1283 .BR size[.{soft|hard|unchecked}]=<integer> ,
1286 is the maximum number of entries slapd will return answering a search
1288 If no size limit is explicitly requested by the client, the
1290 limit is used; if the requested size limit exceeds the
1293 .\".I "Administrative limit exceeded"
1294 .\"error is returned.
1295 limit, the value of the limit is used instead.
1298 limit is set to the keyword
1300 the soft limit is used in either case; if it is set to the keyword
1302 no hard limit is enforced.
1303 Explicit requests for size limits smaller or equal to the
1308 specifier sets a limit on the number of candidates a search request is allowed
1310 The rationale behind it is that searches for non-properly indexed
1311 attributes may result in large sets of candidates, which must be
1314 to determine whether they match the search filter or not.
1317 limit provides a means to drop such operations before they are even
1319 If the selected candidates exceed the
1321 limit, the search will abort with
1322 .IR "Unwilling to perform" .
1323 If it is set to the keyword
1325 no limit is applied (the default).
1328 the search is not even performed; this can be used to disallow searches
1329 for a specific set of users.
1330 If no limit specifier is set, the value is assigned to the
1336 to preserve the original behavior.
1338 In case of no match, the global limits are used.
1339 The default values are the same of
1348 control is requested, the
1350 size limit is used by default, because the request of a specific page size
1351 is considered an explicit request for a limitation on the number
1352 of entries to be returned.
1353 However, the size limit applies to the total count of entries returned within
1354 the search, and not to a single page.
1355 Additional size limits may be enforced; the syntax is
1356 .BR size.pr={<integer>|noEstimate|unlimited} ,
1359 is the max page size if no explicit limit is set; the keyword
1361 inhibits the server from returning an estimate of the total number
1362 of entries that might be returned
1363 (note: the current implementation does not return any estimate).
1366 indicates that no limit is applied to the pagedResults control page size.
1368 .B size.prtotal={<integer>|unlimited|disabled}
1369 allows to set a limit on the total number of entries that a pagedResults
1370 control allows to return.
1371 By default it is set to the
1376 is the max number of entries that the whole search with pagedResults control
1380 to allow unlimited number of entries to be returned, e.g. to allow
1381 the use of the pagedResults control as a means to circumvent size
1382 limitations on regular searches; the keyword
1384 disables the control, i.e. no paged results can be returned.
1385 Note that the total number of entries returned when the pagedResults control
1386 is requested cannot exceed the
1388 size limit of regular searches unless extended by the
1392 The \fBlimits\fP statement is typically used to let an unlimited
1393 number of entries be returned by searches performed
1394 with the identity used by the consumer for synchronization purposes
1395 by means of the RFC 4533 LDAP Content Synchronization protocol
1396 (see \fBsyncrepl\fP for details).
1399 .B maxderefdepth <depth>
1400 Specifies the maximum number of aliases to dereference when trying to
1401 resolve an entry, used to avoid infinite alias loops. The default is 15.
1403 .B mirrormode on | off
1404 This option puts a replica database into "mirror" mode. Update
1405 operations will be accepted from any user, not just the updatedn. The
1406 database must already be configured as a syncrepl consumer
1407 before this keyword may be set. This mode also requires a
1409 (see above) to be configured.
1410 By default, mirrormode is off.
1412 .B monitoring on | off
1413 This option enables database-specific monitoring in the entry related
1414 to the current database in the "cn=Databases,cn=Monitor" subtree
1415 of the monitor database, if the monitor database is enabled.
1416 Currently, only the BDB and the HDB databases provide database-specific
1418 The default depends on the backend type.
1420 .B overlay <overlay-name>
1421 Add the specified overlay to this database. An overlay is a piece of
1422 code that intercepts database operations in order to extend or change
1423 them. Overlays are pushed onto
1424 a stack over the database, and so they will execute in the reverse
1425 of the order in which they were configured and the database itself
1426 will receive control last of all. See the
1427 .BR slapd.overlays (5)
1428 manual page for an overview of the available overlays.
1429 Note that all of the database's
1430 regular settings should be configured before any overlay settings.
1432 .B readonly on | off
1433 This option puts the database into "read-only" mode. Any attempts to
1434 modify the database will return an "unwilling to perform" error. By
1435 default, readonly is off.
1437 .B restrict <oplist>
1438 Specify a whitespace separated list of operations that are restricted.
1439 If defined inside a database specification, restrictions apply only
1440 to that database, otherwise they are global.
1441 Operations can be any of
1446 .BR extended[=<OID>] ,
1450 or the special pseudo-operations
1454 which respectively summarize read and write operations.
1462 keyword allows to indicate the OID of the specific operation
1466 Specify the distinguished name that is not subject to access control
1467 or administrative limit restrictions for operations on this database.
1468 This DN may or may not be associated with an entry. An empty root
1469 DN (the default) specifies no root access is to be granted. It is
1470 recommended that the rootdn only be specified when needed (such as
1471 when initially populating a database). If the rootdn is within
1472 a namingContext (suffix) of the database, a simple bind password
1473 may also be provided using the
1475 directive. Many optional features, including syncrepl, require the
1476 rootdn to be defined for the database.
1478 .B rootpw <password>
1479 Specify a password (or hash of the password) for the rootdn. The
1480 password can only be set if the rootdn is within the namingContext
1481 (suffix) of the database.
1482 This option accepts all RFC 2307 userPassword formats known to
1485 description) as well as cleartext.
1487 may be used to generate a hash of a password. Cleartext
1488 and \fB{CRYPT}\fP passwords are not recommended. If empty
1489 (the default), authentication of the root DN is by other means
1490 (e.g. SASL). Use of SASL is encouraged.
1492 .B suffix <dn suffix>
1493 Specify the DN suffix of queries that will be passed to this
1494 backend database. Multiple suffix lines can be given and at least one is
1495 required for each database definition.
1496 If the suffix of one database is "inside" that of another, the database
1497 with the inner suffix must come first in the configuration file.
1499 .B subordinate [advertise]
1500 Specify that the current backend database is a subordinate of another
1501 backend database. A subordinate database may have only one suffix. This
1502 option may be used to glue multiple databases into a single namingContext.
1503 If the suffix of the current database is within the namingContext of a
1504 superior database, searches against the superior database will be
1505 propagated to the subordinate as well. All of the databases
1506 associated with a single namingContext should have identical rootdns.
1507 Behavior of other LDAP operations is unaffected by this setting. In
1508 particular, it is not possible to use moddn to move an entry from
1509 one subordinate to another subordinate within the namingContext.
1511 If the optional \fBadvertise\fP flag is supplied, the naming context of
1512 this database is advertised in the root DSE. The default is to hide this
1513 database context, so that only the superior context is visible.
1520 are used on the superior database, any glued subordinates that support
1521 these tools are opened as well.
1523 Databases that are glued together should usually be configured with the
1524 same indices (assuming they support indexing), even for attributes that
1525 only exist in some of these databases. In general, all of the glued
1526 databases should be configured as similarly as possible, since the intent
1527 is to provide the appearance of a single directory.
1529 Note that the \fIsubordinate\fP functionality is implemented internally
1530 by the \fIglue\fP overlay and as such its behavior will interact with other
1531 overlays in use. By default, the glue overlay is automatically configured as
1532 the last overlay on the superior backend. Its position on the backend
1533 can be explicitly configured by setting an \fBoverlay glue\fP directive
1534 at the desired position. This explicit configuration is necessary e.g.
1535 when using the \fIsyncprov\fP overlay, which needs to follow \fIglue\fP
1536 in order to work over all of the glued databases. E.g.
1540 suffix dc=example,dc=com
1548 .B syncrepl rid=<replica ID>
1549 .B provider=ldap[s]://<hostname>[:port]
1550 .B searchbase=<base DN>
1551 .B [type=refreshOnly|refreshAndPersist]
1552 .B [interval=dd:hh:mm:ss]
1553 .B [retry=[<retry interval> <# of retries>]+]
1554 .B [filter=<filter str>]
1555 .B [scope=sub|one|base|subord]
1556 .B [attrs=<attr list>]
1558 .B [sizelimit=<limit>]
1559 .B [timelimit=<limit>]
1560 .B [schemachecking=on|off]
1561 .B [network-timeout=<seconds>]
1562 .B [timeout=<seconds>]
1563 .B [bindmethod=simple|sasl]
1565 .B [saslmech=<mech>]
1566 .B [authcid=<identity>]
1567 .B [authzid=<identity>]
1568 .B [credentials=<passwd>]
1570 .B [secprops=<properties>]
1571 .B [starttls=yes|critical]
1572 .B [tls_cert=<file>]
1574 .B [tls_cacert=<file>]
1575 .B [tls_cacertdir=<path>]
1576 .B [tls_reqcert=never|allow|try|demand]
1577 .B [tls_ciphersuite=<ciphers>]
1578 .B [tls_crlcheck=none|peer|all]
1579 .B [logbase=<base DN>]
1580 .B [logfilter=<filter str>]
1581 .B [syncdata=default|accesslog|changelog]
1583 Specify the current database as a replica which is kept up-to-date with the
1584 master content by establishing the current
1586 as a replication consumer site running a
1589 The replica content is kept synchronized to the master content using
1590 the LDAP Content Synchronization protocol. Refer to the
1591 "OpenLDAP Administrator's Guide" for detailed information on
1592 setting up a replicated
1594 directory service using the
1599 identifies the current
1601 directive within the replication consumer site.
1602 It is a non-negative integer not greater than 4095 (limited
1603 to three hexadecimal digits).
1606 specifies the replication provider site containing the master content
1607 as an LDAP URI. If <port> is not given, the standard LDAP port number
1608 (389 or 636) is used.
1612 replica is defined using a search
1613 specification as its result set. The consumer
1615 will send search requests to the provider
1617 according to the search specification. The search specification includes
1618 .BR searchbase ", " scope ", " filter ", " attrs ", " attrsonly ", " sizelimit ", "
1621 parameters as in the normal search specification.
1622 The \fBscope\fP defaults to \fBsub\fP, the \fBfilter\fP defaults to
1623 \fB(objectclass=*)\fP, while there is no default \fBsearchbase\fP. The
1624 \fBattrs\fP list defaults to \fB"*,+"\fP to return all user and operational
1625 attributes, and \fBattrsonly\fP is unset by default.
1626 The \fBsizelimit\fP and \fBtimelimit\fP only
1627 accept "unlimited" and positive integers, and both default to "unlimited".
1628 The \fBsizelimit\fP and \fBtimelimit\fP parameters define
1629 a consumer requested limitation on the number of entries that can be returned
1630 by the LDAP Content Synchronization operation; as such, it is intended
1631 to implement partial replication based on the size of the replicated database
1632 and on the time required by the synchronization.
1633 Note, however, that any provider-side limits for the replication identity
1634 will be enforced by the provider regardless of the limits requested
1635 by the LDAP Content Synchronization operation, much like for any other
1638 The LDAP Content Synchronization protocol has two operation types.
1641 operation, the next synchronization search operation
1642 is periodically rescheduled at an interval time (specified by
1644 parameter; 1 day by default)
1645 after each synchronization operation finishes.
1647 .B refreshAndPersist
1648 operation, a synchronization search remains persistent in the provider slapd.
1649 Further updates to the master replica will generate
1650 .B searchResultEntry
1651 to the consumer slapd as the search responses to the persistent
1652 synchronization search.
1654 If an error occurs during replication, the consumer will attempt to
1655 reconnect according to the
1657 parameter which is a list of the <retry interval> and <# of retries> pairs.
1658 For example, retry="60 10 300 3" lets the consumer retry every 60 seconds
1659 for the first 10 times and then retry every 300 seconds for the next 3
1660 times before stop retrying. The `+' in <# of retries> means indefinite
1661 number of retries until success.
1663 The schema checking can be enforced at the LDAP Sync
1664 consumer site by turning on the
1666 parameter. The default is \fBoff\fP.
1667 Schema checking \fBon\fP means that replicated entries must have
1668 a structural objectClass, must obey to objectClass requirements
1669 in terms of required/allowed attributes, and that naming attributes
1670 and distinguished values must be present.
1671 As a consequence, schema checking should be \fBoff\fP when partial
1672 replication is used.
1676 parameter sets how long the consumer will wait to establish a
1677 network connection to the provider. Once a connection is
1680 parameter determines how long the consumer will wait for the initial
1681 Bind request to complete. The defaults for these parameters come
1689 requires the options
1693 and should only be used when adequate security services
1694 (e.g. TLS or IPSEC) are in place.
1695 .B REMEMBER: simple bind credentials must be in cleartext!
1702 Depending on the mechanism, an authentication identity and/or
1703 credentials can be specified using
1709 parameter may be used to specify an authorization identity.
1710 Specific security properties (as with the
1712 keyword above) for a SASL bind can be set with the
1714 option. A non default SASL realm can be set with the
1717 The identity used for synchronization by the consumer should be allowed
1718 to receive an unlimited number of entries in response to a search request.
1719 The provider, other than allow authentication of the syncrepl identity,
1720 should grant that identity appropriate access privileges to the data
1721 that is being replicated (\fBaccess\fP directive), and appropriate time
1723 This can be accomplished by either allowing unlimited \fBsizelimit\fP
1724 and \fBtimelimit\fP, or by setting an appropriate \fBlimits\fP statement
1725 in the consumer's configuration (see \fBsizelimit\fP and \fBlimits\fP
1730 parameter specifies use of the StartTLS extended operation
1731 to establish a TLS session before Binding to the provider. If the
1733 argument is supplied, the session will be aborted if the StartTLS request
1734 fails. Otherwise the syncrepl session continues without TLS. The
1735 tls_reqcert setting defaults to "demand" and the other TLS settings
1736 default to the same as the main slapd TLS settings.
1738 Rather than replicating whole entries, the consumer can query logs of
1739 data modifications. This mode of operation is referred to as \fIdelta
1740 syncrepl\fP. In addition to the above parameters, the
1744 parameters must be set appropriately for the log that will be used. The
1746 parameter must be set to either "accesslog" if the log conforms to the
1747 .BR slapo-accesslog (5)
1748 log format, or "changelog" if the log conforms
1749 to the obsolete \fIchangelog\fP format. If the
1751 parameter is omitted or set to "default" then the log parameters are
1756 This option is only applicable in a slave
1758 It specifies the DN permitted to update (subject to access controls)
1759 the replica. It is only needed in certain push-mode
1760 replication scenarios. Generally, this DN
1767 Specify the referral to pass back when
1769 is asked to modify a replicated local database.
1770 If specified multiple times, each url is provided.
1772 .SH DATABASE-SPECIFIC OPTIONS
1773 Each database may allow specific configuration options; they are
1774 documented separately in the backends' manual pages. See the
1775 .BR slapd.backends (5)
1776 manual page for an overview of available backends.
1779 Here is a short example of a configuration file:
1783 include SYSCONFDIR/schema/core.schema
1784 pidfile LOCALSTATEDIR/run/slapd.pid
1786 # Subtypes of "name" (e.g. "cn" and "ou") with the
1787 # option ";x-hidden" can be searched for/compared,
1788 # but are not shown. See \fBslapd.access\fP(5).
1789 attributeoptions x-hidden lang-
1790 access to attrs=name;x-hidden by * =cs
1792 # Protect passwords. See \fBslapd.access\fP(5).
1793 access to attrs=userPassword by * auth
1794 # Read access to other attributes and entries.
1795 access to * by * read
1798 suffix "dc=our-domain,dc=com"
1799 # The database directory MUST exist prior to
1800 # running slapd AND should only be accessible
1801 # by the slapd/tools. Mode 0700 recommended.
1802 directory LOCALSTATEDIR/openldap-data
1803 # Indices to maintain
1804 index objectClass eq
1805 index cn,sn,mail pres,eq,approx,sub
1807 # We serve small clients that do not handle referrals,
1808 # so handle remote lookups on their behalf.
1811 uri ldap://ldap.some-server.com/
1816 "OpenLDAP Administrator's Guide" contains a longer annotated
1817 example of a configuration file.
1818 The original ETCDIR/slapd.conf is another example.
1822 default slapd configuration file
1825 .BR slapd\-config (5),
1826 .BR slapd.access (5),
1827 .BR slapd.backends (5),
1828 .BR slapd.overlays (5),
1829 .BR slapd.plugin (5),
1830 .BR slapd.replog (5),
1841 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
1842 .SH ACKNOWLEDGEMENTS