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
323 .B authz-regexp <match> <replace>
324 Used by the authentication framework to convert simple user names,
325 such as provided by SASL subsystem, to an LDAP DN used for
326 authorization purposes. Note that the resultant DN need not refer
327 to an existing entry to be considered valid. When an authorization
328 request is received from the SASL subsystem, the SASL
333 are taken, when available, and combined into a name of the form
337 .B UID=<username>[[,CN=<realm>],CN=<mechanism>],CN=auth
340 This name is then compared against the
342 POSIX (''extended'') regular expression, and if the match is successful,
343 the name is replaced with the
345 string. If there are wildcard strings in the
347 regular expression that are enclosed in parenthesis, e.g.
353 then the portion of the name that matched the wildcard will be stored
354 in the numbered placeholder variable $1. If there are other wildcard strings
355 in parenthesis, the matching strings will be in $2, $3, etc. up to $9. The
356 placeholders can then be used in the
361 .B UID=$1,OU=Accounts,DC=example,DC=com
364 The replaced name can be either a DN, i.e. a string prefixed by "dn:",
366 If the latter, the server will use the URI to search its own database(s)
367 and, if the search returns exactly one entry, the name is
368 replaced by the DN of that entry. The LDAP URI must have no
369 hostport, attrs, or extensions components, but the filter is mandatory,
373 .B ldap:///OU=Accounts,DC=example,DC=com??one?(UID=$1)
376 The protocol portion of the URI must be strictly
378 Note that this search is subject to access controls. Specifically,
379 the authentication identity must have "auth" access in the subject.
383 options can be given in the configuration file to allow for multiple matching
384 and replacement patterns. The matching patterns are checked in the order they
385 appear in the file, stopping at the first successful match.
388 .\"Because the plus sign + is a character recognized by the regular expression engine,
389 .\"and it will appear in names that include a REALM, be careful to escape the
390 .\"plus sign with a backslash \\+ to remove the character's special meaning.
393 .B concurrency <integer>
394 Specify a desired level of concurrency. Provided to the underlying
395 thread system as a hint. The default is not to provide any hint.
397 .B conn_max_pending <integer>
398 Specify the maximum number of pending requests for an anonymous session.
399 If requests are submitted faster than the server can process them, they
400 will be queued up to this limit. If the limit is exceeded, the session
401 is closed. The default is 100.
403 .B conn_max_pending_auth <integer>
404 Specify the maximum number of pending requests for an authenticated session.
407 .B defaultsearchbase <dn>
408 Specify a default search base to use when client submits a
409 non-base search request with an empty base DN.
410 Base scoped search requests with an empty base DN are not affected.
412 .B disallow <features>
413 Specify a set of features (separated by white space) to
414 disallow (default none).
416 disables acceptance of anonymous bind requests. Note that this setting
417 does not prohibit anonymous directory access (See "require authc").
419 disables simple (bind) authentication.
421 disables forcing session to anonymous status (see also
423 upon StartTLS operation receipt.
425 disallows the StartTLS operation if authenticated (see also
429 .B ditcontentrule "(\ <oid>\
431 [DESC\ <description>]\
438 Specify an DIT Content Rule using the LDAPv3 syntax defined in RFC 4512.
439 The slapd parser extends the RFC 4512 definition by allowing string
440 forms as well as numeric OIDs to be used for the attribute OID and
441 attribute syntax OID.
447 .B gentlehup { on | off }
448 A SIGHUP signal will only cause a 'gentle' shutdown-attempt:
450 will stop listening for new connections, but will not close the
451 connections to the current clients. Future write operations return
452 unwilling-to-perform, though. Slapd terminates when all clients
453 have closed their connections (if they ever do), or \- as before \-
454 if it receives a SIGTERM signal. This can be useful if you wish to
455 terminate the server and start a new
458 .B with another database,
459 without disrupting the currently active clients.
460 The default is off. You may wish to use
462 along with this option.
464 .B idletimeout <integer>
465 Specify the number of seconds to wait before forcibly closing
466 an idle client connection. A idletimeout of 0 disables this
467 feature. The default is 0.
469 .B include <filename>
470 Read additional configuration information from the given file before
471 continuing with the next line of the current file.
473 .B index_intlen <integer>
474 Specify the key length for ordered integer indices. The most significant
475 bytes of the binary integer will be used for index keys. The default
476 value is 4, which provides exact indexing for 31 bit values.
477 A floating point representation is used to index too large values.
479 .B index_substr_if_minlen <integer>
480 Specify the minimum length for subinitial and subfinal indices. An
481 attribute value must have at least this many characters in order to be
482 processed by the indexing functions. The default is 2.
484 .B index_substr_if_maxlen <integer>
485 Specify the maximum length for subinitial and subfinal indices. Only
486 this many characters of an attribute value will be processed by the
487 indexing functions; any excess characters are ignored. The default is 4.
489 .B index_substr_any_len <integer>
490 Specify the length used for subany indices. An attribute value must have
491 at least this many characters in order to be processed. Attribute values
492 longer than this length will be processed in segments of this length. The
493 default is 4. The subany index will also be used in subinitial and
494 subfinal index lookups when the filter string is longer than the
495 .I index_substr_if_maxlen
498 .B index_substr_any_step <integer>
499 Specify the steps used in subany index lookups. This value sets the offset
500 for the segments of a filter string that are processed for a subany index
501 lookup. The default is 2. For example, with the default values, a search
502 using this filter "cn=*abcdefgh*" would generate index lookups for
503 "abcd", "cdef", and "efgh".
506 Note: Indexing support depends on the particular backend in use. Also,
507 changing these settings will generally require deleting any indices that
508 depend on these parameters and recreating them with
513 Specifies the Security Strength Factor (SSF) to be given local LDAP sessions,
514 such as those to the ldapi:// listener. For a description of SSF values,
518 option description. The default is 71.
520 .B logfile <filename>
521 Specify a file for recording debug log messages. By default these messages
522 only go to stderr and are not recorded anywhere else. Specifying a logfile
523 copies messages to both stderr and the logfile.
525 .B loglevel <integer> [...]
526 Specify the level at which debugging statements and operation
527 statistics should be syslogged (currently logged to the
529 LOG_LOCAL4 facility).
530 They must be considered subsystems rather than increasingly verbose
532 Some messages with higher priority are logged regardless
533 of the configured loglevel as soon as any logging is configured.
534 Log levels are additive, and available levels are:
545 debug packet handling
549 heavy trace debugging (function args)
553 connection management
557 print out packets sent and received
561 search filter processing
565 configuration file processing
569 access control list processing
573 connections, LDAP operations, results (recommended)
577 stats log entries sent
581 print communication with shell backends
593 \"data indexing (unused)
601 only messages that get logged whatever log level is set
604 The desired log level can be input as a single integer that combines
605 the (ORed) desired levels, both in decimal or in hexadecimal notation,
606 as a list of integers (that are ORed internally),
607 or as a list of the names that are shown between brackets, such that
620 can be used as a shortcut to enable logging at all levels (equivalent to -1).
623 or the equivalent integer representation, causes those messages
624 that are logged regardless of the configured loglevel to be logged.
625 In fact, if loglevel is set to 0, no logging occurs,
628 level is required to have high priority messages logged.
630 The loglevel defaults to \fBstats\fP.
631 This level should usually also be included when using other loglevels, to
632 help analyze the logs.
635 .B moduleload <filename>
636 Specify the name of a dynamically loadable module to load. The filename
637 may be an absolute path name or a simple filename. Non-absolute names
638 are searched for in the directories specified by the
640 option. This option and the
642 option are only usable if slapd was compiled with --enable-modules.
644 .B modulepath <pathspec>
645 Specify a list of directories to search for loadable modules. Typically
646 the path is colon-separated but this depends on the operating system.
649 .B objectclass "(\ <oid>\
651 [DESC\ <description>]\
654 [{ ABSTRACT | STRUCTURAL | AUXILIARY }]\
655 [MUST\ <oids>] [MAY\ <oids>] )"
657 Specify an objectclass using the LDAPv3 syntax defined in RFC 4512.
658 The slapd parser extends the RFC 4512 definition by allowing string
659 forms as well as numeric OIDs to be used for the object class OID.
663 description.) Object classes are "STRUCTURAL" by default.
666 .B objectidentifier <name> "{ <oid> | <name>[:<suffix>] }"
667 Define a string name that equates to the given OID. The string can be used
668 in place of the numeric OID in objectclass and attribute definitions. The
669 name can also be used with a suffix of the form ":xx" in which case the
670 value "oid.xx" will be used.
672 .B password-hash <hash> [<hash>...]
673 This option configures one or more hashes to be used in generation of user
674 passwords stored in the userPassword attribute during processing of
675 LDAP Password Modify Extended Operations (RFC 3062).
676 The <hash> must be one of
690 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
695 use the MD5 algorithm (RFC 1321), the latter with a seed.
702 indicates that the new password should be
703 added to userPassword as clear text.
705 Note that this option does not alter the normal user applications
706 handling of userPassword during LDAP Add, Modify, or other LDAP operations.
708 .B password\-crypt\-salt\-format <format>
709 Specify the format of the salt passed to
711 when generating {CRYPT} passwords (see
713 during processing of LDAP Password Modify Extended Operations (RFC 3062).
715 This string needs to be in
717 format and may include one (and only one) %s conversion.
718 This conversion will be substituted with a string of random
719 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
720 provides a two character salt and "$1$%.8s" tells some
721 versions of crypt(3) to use an MD5 algorithm and provides
722 8 random characters of salt. The default is "%s", which
723 provides 31 characters of salt.
725 .B pidfile <filename>
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.
733 Specify the referral to pass back when
735 cannot find a local database to handle a request.
736 If specified multiple times, each url is provided.
738 .B require <conditions>
739 Specify a set of conditions (separated by white space) to
740 require (default none).
741 The directive may be specified globally and/or per-database;
742 databases inherit global conditions, so per-database specifications
745 requires bind operation prior to directory operations.
747 requires session to be using LDAP version 3.
749 requires authentication prior to directory operations.
751 requires SASL authentication prior to directory operations.
753 requires strong authentication prior to directory operations.
754 The strong keyword allows protected "simple" authentication
755 as well as SASL authentication.
757 may be used to require no conditions (useful to clear out globally
758 set conditions within a particular database); it must occur first
759 in the list of conditions.
761 .B reverse-lookup on | off
762 Enable/disable client name unverified reverse lookup (default is
764 if compiled with --enable-rlookups).
767 Specify the name of an LDIF(5) file containing user defined attributes
768 for the root DSE. These attributes are returned in addition to the
769 attributes normally produced by slapd.
771 The root DSE is an entry with information about the server and its
772 capabilities, in operational attributes.
773 It has the empty DN, and can be read with e.g.:
775 ldapsearch -x -b "" -s base "+"
777 See RFC 4512 section 5.1 for details.
780 Used to specify the fully qualified domain name used for SASL processing.
782 .B sasl-realm <realm>
783 Specify SASL realm. Default is empty.
785 .B sasl-secprops <properties>
786 Used to specify Cyrus SASL security properties.
789 flag (without any other properties) causes the flag properties
790 default, "noanonymous,noplain", to be cleared.
793 flag disables mechanisms susceptible to simple passive attacks.
796 flag disables mechanisms susceptible to active attacks.
799 flag disables mechanisms susceptible to passive dictionary attacks.
802 flag disables mechanisms which support anonymous login.
805 flag require forward secrecy between sessions.
808 require mechanisms which pass client credentials (and allow
809 mechanisms which can pass credentials to do so).
812 property specifies the minimum acceptable
813 .I security strength factor
814 as an integer approximate to effective key length used for
815 encryption. 0 (zero) implies no protection, 1 implies integrity
816 protection only, 56 allows DES or other weak ciphers, 112
817 allows triple DES and other strong ciphers, 128 allows RC4,
818 Blowfish and other modern strong ciphers. The default is 0.
821 property specifies the maximum acceptable
822 .I security strength factor
823 as an integer (see minssf description). The default is INT_MAX.
826 property specifies the maximum security layer receive buffer
827 size allowed. 0 disables security layers. The default is 65536.
830 Specify the distinguished name for the subschema subentry that
831 controls the entries on this server. The default is "cn=Subschema".
833 .B security <factors>
834 Specify a set of security strength factors (separated by white space)
838 option for a description of security strength factors).
839 The directive may be specified globally and/or per-database.
841 specifies the overall security strength factor.
843 specifies the transport security strength factor.
845 specifies the TLS security strength factor.
847 specifies the SASL security strength factor.
849 specifies the overall security strength factor to require for
851 .B update_transport=<n>
852 specifies the transport security strength factor to require for
855 specifies the TLS security strength factor to require for
858 specifies the SASL security strength factor to require for
861 specifies the security strength factor required for
863 username/password authentication.
866 factor is measure of security provided by the underlying transport,
867 e.g. ldapi:// (and eventually IPSEC). It is not normally used.
869 .B serverID <integer> [<URL>]
870 Specify an integer ID from 0 to 4095 for this server (limited
871 to 3 hexadecimal digits).
873 required when using multimaster replication and each master must have a
874 unique ID. Note that this requirement also applies to separate masters
875 contributing to a glued set of databases.
876 If the URL is provided, this directive may be specified
877 multiple times, providing a complete list of participating servers
878 and their IDs. The fully qualified hostname of each server should be
879 used in the supplied URLs. The IDs are used in the "replica id" field
880 of all CSNs generated by the specified server. The default value is zero.
887 .B sizelimit {<integer>|unlimited}
889 .B sizelimit size[.{soft|hard|unchecked}]=<integer> [...]
890 Specify the maximum number of entries to return from a search operation.
891 The default size limit is 500.
894 to specify no limits.
895 The second format allows a fine grain setting of the size limits.
896 Extra args can be added on the same line.
899 for an explanation of the different flags.
901 .B sockbuf_max_incoming <integer>
902 Specify the maximum incoming LDAP PDU size for anonymous sessions.
903 The default is 262143.
905 .B sockbuf_max_incoming_auth <integer>
906 Specify the maximum incoming LDAP PDU size for authenticated sessions.
907 The default is 4194303.
909 .B sortvals <attr> [...]
910 Specify a list of multi-valued attributes whose values will always
911 be maintained in sorted order. Using this option will allow Modify,
912 Compare, and filter evaluations on these attributes to be performed
913 more efficiently. The resulting sort order depends on the
914 attributes' syntax and matching rules and may not correspond to
915 lexical order or any other recognizable order.
918 Specify the maximum size of the primary thread pool.
919 The default is 16; the minimum value is 2.
921 .B timelimit {<integer>|unlimited}
923 .B timelimit time[.{soft|hard}]=<integer> [...]
924 Specify the maximum number of seconds (in real time)
926 will spend answering a search request. The default time limit is 3600.
929 to specify no limits.
930 The second format allows a fine grain setting of the time limits.
931 Extra args can be added on the same line.
934 for an explanation of the different flags.
936 .B tool-threads <integer>
937 Specify the maximum number of threads to use in tool mode.
938 This should not be greater than the number of CPUs in the system.
940 .\"ucdata-path is obsolete / ignored...
942 .\".B ucdata-path <path>
943 .\"Specify the path to the directory containing the Unicode character
944 .\"tables. The default path is DATADIR/ucdata.
948 is built with support for Transport Layer Security, there are more options
951 .B TLSCipherSuite <cipher-suite-spec>
952 Permits configuring what ciphers will be accepted and the preference order.
953 <cipher-suite-spec> should be a cipher specification for OpenSSL. Example:
955 TLSCipherSuite HIGH:MEDIUM:+SSLv2
957 To check what ciphers a given spec selects, use:
960 openssl ciphers -v <cipher-suite-spec>
963 To obtain the list of ciphers in GNUtls use:
970 .B TLSCACertificateFile <filename>
971 Specifies the file that contains certificates for all of the Certificate
976 .B TLSCACertificatePath <path>
977 Specifies the path of a directory that contains Certificate Authority
978 certificates in separate individual files. Usually only one of this
979 or the TLSCACertificateFile is used. This directive is not supported
982 .B TLSCertificateFile <filename>
983 Specifies the file that contains the
987 .B TLSCertificateKeyFile <filename>
988 Specifies the file that contains the
990 server private key that matches the certificate stored in the
991 .B TLSCertificateFile
992 file. Currently, the private key must not be protected with a password, so
993 it is of critical importance that it is protected carefully.
995 .B TLSDHParamFile <filename>
996 This directive specifies the file that contains parameters for Diffie-Hellman
997 ephemeral key exchange. This is required in order to use a DSA certificate on
998 the server. If multiple sets of parameters are present in the file, all of
999 them will be processed. Note that setting this option may also enable
1000 Anonymous Diffie-Hellman key exchanges in certain non-default cipher suites.
1001 You should append "!ADH" to your cipher suites if you have changed them
1002 from the default, otherwise no certificate exchanges or verification will
1003 be done. When using GNUtls these parameters are always generated randomly so
1004 this directive is ignored.
1006 .B TLSRandFile <filename>
1007 Specifies the file to obtain random bits from when /dev/[u]random
1008 is not available. Generally set to the name of the EGD/PRNGD socket.
1009 The environment variable RANDFILE can also be used to specify the filename.
1010 This directive is ignored with GNUtls.
1012 .B TLSVerifyClient <level>
1013 Specifies what checks to perform on client certificates in an
1014 incoming TLS session, if any.
1017 can be specified as one of the following keywords:
1021 This is the default.
1023 will not ask the client for a certificate.
1026 The client certificate is requested. If no certificate is provided,
1027 the session proceeds normally. If a bad certificate is provided,
1028 it will be ignored and the session proceeds normally.
1031 The client certificate is requested. If no certificate is provided,
1032 the session proceeds normally. If a bad certificate is provided,
1033 the session is immediately terminated.
1035 .B demand | hard | true
1036 These keywords are all equivalent, for compatibility reasons.
1037 The client certificate is requested. If no certificate is provided,
1038 or a bad certificate is provided, the session is immediately terminated.
1040 Note that a valid client certificate is required in order to use the
1041 SASL EXTERNAL authentication mechanism with a TLS session. As such,
1044 setting must be chosen to enable SASL EXTERNAL authentication.
1047 .B TLSCRLCheck <level>
1048 Specifies if the Certificate Revocation List (CRL) of the CA should be
1049 used to verify if the client certificates have not been revoked. This
1051 .B TLSCACertificatePath
1052 parameter to be set. This directive is ignored with GNUtls.
1054 can be specified as one of the following keywords:
1058 No CRL checks are performed
1061 Check the CRL of the peer certificate
1064 Check the CRL for a whole certificate chain
1067 .B TLSCRLFile <filename>
1068 Specifies a file containing a Certificate Revocation List to be used
1069 for verifying that certificates have not been revoked. This directive is
1070 only valid when using GNUtls.
1071 .SH GENERAL BACKEND OPTIONS
1072 Options in this section only apply to the configuration file section
1073 for the specified backend. They are supported by every
1076 .B backend <databasetype>
1077 Mark the beginning of a backend definition. <databasetype>
1094 depending on which backend will serve the database.
1096 .SH GENERAL DATABASE OPTIONS
1097 Options in this section only apply to the configuration file section
1098 for the database in which they are defined. They are supported by every
1099 type of backend. Note that the
1103 option are mandatory for each database.
1105 .B database <databasetype>
1106 Mark the beginning of a new database instance definition. <databasetype>
1123 depending on which backend will serve the database.
1126 Controls whether the database will be used to answer
1127 queries. A database that is hidden will never be
1128 selected to answer any queries, and any suffix configured
1129 on the database will be ignored in checks for conflicts
1130 with other databases. By default, hidden is off.
1135 will automatically maintain the
1136 modifiersName, modifyTimestamp, creatorsName, and
1137 createTimestamp attributes for entries. It also controls
1138 the entryCSN and entryUUID attributes, which are needed
1139 by the syncrepl provider. By default, lastmod is on.
1141 .B limits <who> <limit> [<limit> [...]]
1142 Specify time and size limits based on who initiated an operation.
1149 anonymous | users | [dn[.<style>]=]<pattern> | group[/oc[/at]]=<pattern>
1155 <style> ::= exact | base | onelevel | subtree | children | regex | anonymous
1160 matches all unauthenticated clients.
1163 matches all authenticated clients;
1166 dn pattern is assumed unless otherwise specified by qualifying
1167 the (optional) key string
1173 (which are synonyms), to require an exact match; with
1175 to require exactly one level of depth match; with
1177 to allow any level of depth match, including the exact match; with
1179 to allow any level of depth match, not including the exact match;
1181 explicitly requires the (default) match based on POSIX (''extended'')
1182 regular expression pattern.
1185 matches unbound operations; the
1188 The same behavior is obtained by using the
1195 with the optional objectClass
1201 sets the limits for any DN listed in the values of the
1207 group objectClass (default
1209 whose DN exactly matches
1212 The currently supported limits are
1217 The syntax for time limits is
1218 .BR time[.{soft|hard}]=<integer> ,
1221 is the number of seconds slapd will spend answering a search request.
1222 If no time limit is explicitly requested by the client, the
1224 limit is used; if the requested time limit exceeds the
1227 .\".I "Administrative limit exceeded"
1228 .\"error is returned.
1229 limit, the value of the limit is used instead.
1232 limit is set to the keyword
1234 the soft limit is used in either case; if it is set to the keyword
1236 no hard limit is enforced.
1237 Explicit requests for time limits smaller or equal to the
1240 If no limit specifier is set, the value is assigned to the
1246 to preserve the original behavior.
1248 The syntax for size limits is
1249 .BR size[.{soft|hard|unchecked}]=<integer> ,
1252 is the maximum number of entries slapd will return answering a search
1254 If no size limit is explicitly requested by the client, the
1256 limit is used; if the requested size limit exceeds the
1259 .\".I "Administrative limit exceeded"
1260 .\"error is returned.
1261 limit, the value of the limit is used instead.
1264 limit is set to the keyword
1266 the soft limit is used in either case; if it is set to the keyword
1268 no hard limit is enforced.
1269 Explicit requests for size limits smaller or equal to the
1274 specifier sets a limit on the number of candidates a search request is allowed
1276 The rationale behind it is that searches for non-properly indexed
1277 attributes may result in large sets of candidates, which must be
1280 to determine whether they match the search filter or not.
1283 limit provides a means to drop such operations before they are even
1285 If the selected candidates exceed the
1287 limit, the search will abort with
1288 .IR "Unwilling to perform" .
1289 If it is set to the keyword
1291 no limit is applied (the default).
1294 the search is not even performed; this can be used to disallow searches
1295 for a specific set of users.
1296 If no limit specifier is set, the value is assigned to the
1302 to preserve the original behavior.
1304 In case of no match, the global limits are used.
1305 The default values are the same of
1314 control is requested, the
1316 size limit is used by default, because the request of a specific page size
1317 is considered an explicit request for a limitation on the number
1318 of entries to be returned.
1319 However, the size limit applies to the total count of entries returned within
1320 the search, and not to a single page.
1321 Additional size limits may be enforced; the syntax is
1322 .BR size.pr={<integer>|noEstimate|unlimited} ,
1325 is the max page size if no explicit limit is set; the keyword
1327 inhibits the server from returning an estimate of the total number
1328 of entries that might be returned
1329 (note: the current implementation does not return any estimate).
1332 indicates that no limit is applied to the pagedResults control page size.
1334 .B size.prtotal={<integer>|unlimited|disabled}
1335 allows to set a limit on the total number of entries that a pagedResults
1336 control allows to return.
1337 By default it is set to the
1342 is the max number of entries that the whole search with pagedResults control
1346 to allow unlimited number of entries to be returned, e.g. to allow
1347 the use of the pagedResults control as a means to circumvent size
1348 limitations on regular searches; the keyword
1350 disables the control, i.e. no paged results can be returned.
1351 Note that the total number of entries returned when the pagedResults control
1352 is requested cannot exceed the
1354 size limit of regular searches unless extended by the
1358 The \fBlimits\fP statement is typically used to let an unlimited
1359 number of entries be returned by searches performed
1360 with the identity used by the consumer for synchronization purposes
1361 by means of the RFC 4533 LDAP Content Synchronization protocol
1362 (see \fBsyncrepl\fP for details).
1365 .B maxderefdepth <depth>
1366 Specifies the maximum number of aliases to dereference when trying to
1367 resolve an entry, used to avoid infinite alias loops. The default is 15.
1369 .B mirrormode on | off
1370 This option puts a replica database into "mirror" mode. Update
1371 operations will be accepted from any user, not just the updatedn. The
1372 database must already be configured as a syncrepl consumer
1373 before this keyword may be set. This mode also requires a
1375 (see above) to be configured.
1376 By default, mirrormode is off.
1378 .B monitoring on | off
1379 This option enables database-specific monitoring in the entry related
1380 to the current database in the "cn=Databases,cn=Monitor" subtree
1381 of the monitor database, if the monitor database is enabled.
1382 Currently, only the BDB and the HDB databases provide database-specific
1384 The default depends on the backend type.
1386 .B overlay <overlay-name>
1387 Add the specified overlay to this database. An overlay is a piece of
1388 code that intercepts database operations in order to extend or change
1389 them. Overlays are pushed onto
1390 a stack over the database, and so they will execute in the reverse
1391 of the order in which they were configured and the database itself
1392 will receive control last of all. See the
1393 .BR slapd.overlays (5)
1394 manual page for an overview of the available overlays.
1395 Note that all of the database's
1396 regular settings should be configured before any overlay settings.
1398 .B readonly on | off
1399 This option puts the database into "read-only" mode. Any attempts to
1400 modify the database will return an "unwilling to perform" error. By
1401 default, readonly is off.
1403 .B restrict <oplist>
1404 Specify a whitespace separated list of operations that are restricted.
1405 If defined inside a database specification, restrictions apply only
1406 to that database, otherwise they are global.
1407 Operations can be any of
1412 .BR extended[=<OID>] ,
1416 or the special pseudo-operations
1420 which respectively summarize read and write operations.
1428 keyword allows to indicate the OID of the specific operation
1432 Specify the distinguished name that is not subject to access control
1433 or administrative limit restrictions for operations on this database.
1434 This DN may or may not be associated with an entry. An empty root
1435 DN (the default) specifies no root access is to be granted. It is
1436 recommended that the rootdn only be specified when needed (such as
1437 when initially populating a database). If the rootdn is within
1438 a namingContext (suffix) of the database, a simple bind password
1439 may also be provided using the
1441 directive. Many optional features, including syncrepl, require the
1442 rootdn to be defined for the database.
1444 .B rootpw <password>
1445 Specify a password (or hash of the password) for the rootdn. The
1446 password can only be set if the rootdn is within the namingContext
1447 (suffix) of the database.
1448 This option accepts all RFC 2307 userPassword formats known to
1451 description) as well as cleartext.
1453 may be used to generate a hash of a password. Cleartext
1454 and \fB{CRYPT}\fP passwords are not recommended. If empty
1455 (the default), authentication of the root DN is by other means
1456 (e.g. SASL). Use of SASL is encouraged.
1458 .B suffix <dn suffix>
1459 Specify the DN suffix of queries that will be passed to this
1460 backend database. Multiple suffix lines can be given and at least one is
1461 required for each database definition.
1462 If the suffix of one database is "inside" that of another, the database
1463 with the inner suffix must come first in the configuration file.
1465 .B subordinate [advertise]
1466 Specify that the current backend database is a subordinate of another
1467 backend database. A subordinate database may have only one suffix. This
1468 option may be used to glue multiple databases into a single namingContext.
1469 If the suffix of the current database is within the namingContext of a
1470 superior database, searches against the superior database will be
1471 propagated to the subordinate as well. All of the databases
1472 associated with a single namingContext should have identical rootdns.
1473 Behavior of other LDAP operations is unaffected by this setting. In
1474 particular, it is not possible to use moddn to move an entry from
1475 one subordinate to another subordinate within the namingContext.
1477 If the optional \fBadvertise\fP flag is supplied, the naming context of
1478 this database is advertised in the root DSE. The default is to hide this
1479 database context, so that only the superior context is visible.
1486 are used on the superior database, any glued subordinates that support
1487 these tools are opened as well.
1489 Databases that are glued together should usually be configured with the
1490 same indices (assuming they support indexing), even for attributes that
1491 only exist in some of these databases. In general, all of the glued
1492 databases should be configured as similarly as possible, since the intent
1493 is to provide the appearance of a single directory.
1495 Note that the \fIsubordinate\fP functionality is implemented internally
1496 by the \fIglue\fP overlay and as such its behavior will interact with other
1497 overlays in use. By default, the glue overlay is automatically configured as
1498 the last overlay on the superior backend. Its position on the backend
1499 can be explicitly configured by setting an \fBoverlay glue\fP directive
1500 at the desired position. This explicit configuration is necessary e.g.
1501 when using the \fIsyncprov\fP overlay, which needs to follow \fIglue\fP
1502 in order to work over all of the glued databases. E.g.
1506 suffix dc=example,dc=com
1514 .B syncrepl rid=<replica ID>
1515 .B provider=ldap[s]://<hostname>[:port]
1516 .B searchbase=<base DN>
1517 .B [type=refreshOnly|refreshAndPersist]
1518 .B [interval=dd:hh:mm:ss]
1519 .B [retry=[<retry interval> <# of retries>]+]
1520 .B [filter=<filter str>]
1521 .B [scope=sub|one|base|subord]
1522 .B [attrs=<attr list>]
1524 .B [sizelimit=<limit>]
1525 .B [timelimit=<limit>]
1526 .B [schemachecking=on|off]
1527 .B [network-timeout=<seconds>]
1528 .B [timeout=<seconds>]
1529 .B [bindmethod=simple|sasl]
1531 .B [saslmech=<mech>]
1532 .B [authcid=<identity>]
1533 .B [authzid=<identity>]
1534 .B [credentials=<passwd>]
1536 .B [secprops=<properties>]
1537 .B [starttls=yes|critical]
1538 .B [tls_cert=<file>]
1540 .B [tls_cacert=<file>]
1541 .B [tls_cacertdir=<path>]
1542 .B [tls_reqcert=never|allow|try|demand]
1543 .B [tls_ciphersuite=<ciphers>]
1544 .B [tls_crlcheck=none|peer|all]
1545 .B [logbase=<base DN>]
1546 .B [logfilter=<filter str>]
1547 .B [syncdata=default|accesslog|changelog]
1549 Specify the current database as a replica which is kept up-to-date with the
1550 master content by establishing the current
1552 as a replication consumer site running a
1555 The replica content is kept synchronized to the master content using
1556 the LDAP Content Synchronization protocol. Refer to the
1557 "OpenLDAP Administrator's Guide" for detailed information on
1558 setting up a replicated
1560 directory service using the
1565 identifies the current
1567 directive within the replication consumer site.
1568 It is a non-negative integer not greater than 4095 (limited
1569 to three hexadecimal digits).
1572 specifies the replication provider site containing the master content
1573 as an LDAP URI. If <port> is not given, the standard LDAP port number
1574 (389 or 636) is used.
1578 replica is defined using a search
1579 specification as its result set. The consumer
1581 will send search requests to the provider
1583 according to the search specification. The search specification includes
1584 .BR searchbase ", " scope ", " filter ", " attrs ", " attrsonly ", " sizelimit ", "
1587 parameters as in the normal search specification.
1588 The \fBscope\fP defaults to \fBsub\fP, the \fBfilter\fP defaults to
1589 \fB(objectclass=*)\fP, while there is no default \fBsearchbase\fP. The
1590 \fBattrs\fP list defaults to \fB"*,+"\fP to return all user and operational
1591 attributes, and \fBattrsonly\fP is unset by default.
1592 The \fBsizelimit\fP and \fBtimelimit\fP only
1593 accept "unlimited" and positive integers, and both default to "unlimited".
1594 The \fBsizelimit\fP and \fBtimelimit\fP parameters define
1595 a consumer requested limitation on the number of entries that can be returned
1596 by the LDAP Content Synchronization operation; as such, it is intended
1597 to implement partial replication based on the size of the replicated database
1598 and on the time required by the synchronization.
1599 Note, however, that any provider-side limits for the replication identity
1600 will be enforced by the provider regardless of the limits requested
1601 by the LDAP Content Synchronization operation, much like for any other
1604 The LDAP Content Synchronization protocol has two operation types.
1607 operation, the next synchronization search operation
1608 is periodically rescheduled at an interval time (specified by
1610 parameter; 1 day by default)
1611 after each synchronization operation finishes.
1613 .B refreshAndPersist
1614 operation, a synchronization search remains persistent in the provider slapd.
1615 Further updates to the master replica will generate
1616 .B searchResultEntry
1617 to the consumer slapd as the search responses to the persistent
1618 synchronization search.
1620 If an error occurs during replication, the consumer will attempt to
1621 reconnect according to the
1623 parameter which is a list of the <retry interval> and <# of retries> pairs.
1624 For example, retry="60 10 300 3" lets the consumer retry every 60 seconds
1625 for the first 10 times and then retry every 300 seconds for the next 3
1626 times before stop retrying. The `+' in <# of retries> means indefinite
1627 number of retries until success.
1629 The schema checking can be enforced at the LDAP Sync
1630 consumer site by turning on the
1632 parameter. The default is \fBoff\fP.
1633 Schema checking \fBon\fP means that replicated entries must have
1634 a structural objectClass, must obey to objectClass requirements
1635 in terms of required/allowed attributes, and that naming attributes
1636 and distinguished values must be present.
1637 As a consequence, schema checking should be \fBoff\fP when partial
1638 replication is used.
1642 parameter sets how long the consumer will wait to establish a
1643 network connection to the provider. Once a connection is
1646 parameter determines how long the consumer will wait for the initial
1647 Bind request to complete. The defaults for these parameters come
1655 requires the options
1659 and should only be used when adequate security services
1660 (e.g. TLS or IPSEC) are in place.
1661 .B REMEMBER: simple bind credentials must be in cleartext!
1668 Depending on the mechanism, an authentication identity and/or
1669 credentials can be specified using
1675 parameter may be used to specify an authorization identity.
1676 Specific security properties (as with the
1678 keyword above) for a SASL bind can be set with the
1680 option. A non default SASL realm can be set with the
1683 The identity used for synchronization by the consumer should be allowed
1684 to receive an unlimited number of entries in response to a search request.
1685 The provider, other than allow authentication of the syncrepl identity,
1686 should grant that identity appropriate access privileges to the data
1687 that is being replicated (\fBaccess\fP directive), and appropriate time
1689 This can be accomplished by either allowing unlimited \fBsizelimit\fP
1690 and \fBtimelimit\fP, or by setting an appropriate \fBlimits\fP statement
1691 in the consumer's configuration (see \fBsizelimit\fP and \fBlimits\fP
1696 parameter specifies use of the StartTLS extended operation
1697 to establish a TLS session before Binding to the provider. If the
1699 argument is supplied, the session will be aborted if the StartTLS request
1700 fails. Otherwise the syncrepl session continues without TLS. The
1701 tls_reqcert setting defaults to "demand" and the other TLS settings
1702 default to the same as the main slapd TLS settings.
1704 Rather than replicating whole entries, the consumer can query logs of
1705 data modifications. This mode of operation is referred to as \fIdelta
1706 syncrepl\fP. In addition to the above parameters, the
1710 parameters must be set appropriately for the log that will be used. The
1712 parameter must be set to either "accesslog" if the log conforms to the
1713 .BR slapo-accesslog (5)
1714 log format, or "changelog" if the log conforms
1715 to the obsolete \fIchangelog\fP format. If the
1717 parameter is omitted or set to "default" then the log parameters are
1722 This option is only applicable in a slave
1724 It specifies the DN permitted to update (subject to access controls)
1725 the replica. It is only needed in certain push-mode
1726 replication scenarios. Generally, this DN
1733 Specify the referral to pass back when
1735 is asked to modify a replicated local database.
1736 If specified multiple times, each url is provided.
1738 .SH DATABASE-SPECIFIC OPTIONS
1739 Each database may allow specific configuration options; they are
1740 documented separately in the backends' manual pages. See the
1741 .BR slapd.backends (5)
1742 manual page for an overview of available backends.
1745 Here is a short example of a configuration file:
1749 include SYSCONFDIR/schema/core.schema
1750 pidfile LOCALSTATEDIR/run/slapd.pid
1752 # Subtypes of "name" (e.g. "cn" and "ou") with the
1753 # option ";x-hidden" can be searched for/compared,
1754 # but are not shown. See \fBslapd.access\fP(5).
1755 attributeoptions x-hidden lang-
1756 access to attrs=name;x-hidden by * =cs
1758 # Protect passwords. See \fBslapd.access\fP(5).
1759 access to attrs=userPassword by * auth
1760 # Read access to other attributes and entries.
1761 access to * by * read
1764 suffix "dc=our-domain,dc=com"
1765 # The database directory MUST exist prior to
1766 # running slapd AND should only be accessible
1767 # by the slapd/tools. Mode 0700 recommended.
1768 directory LOCALSTATEDIR/openldap-data
1769 # Indices to maintain
1770 index objectClass eq
1771 index cn,sn,mail pres,eq,approx,sub
1773 # We serve small clients that do not handle referrals,
1774 # so handle remote lookups on their behalf.
1777 uri ldap://ldap.some-server.com/
1782 "OpenLDAP Administrator's Guide" contains a longer annotated
1783 example of a configuration file.
1784 The original ETCDIR/slapd.conf is another example.
1788 default slapd configuration file
1791 .BR slapd\-config (5),
1792 .BR slapd.access (5),
1793 .BR slapd.backends (5),
1794 .BR slapd.overlays (5),
1795 .BR slapd.plugin (5),
1796 .BR slapd.replog (5),
1807 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
1808 .SH ACKNOWLEDGEMENTS
projects / openldap / blob