1 .TH SLAPD.CONF 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2004 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapd.conf \- configuration file for slapd, the stand-alone LDAP daemon
12 contains configuration information for the
14 daemon. This configuration file is also used by the
16 replication daemon and by the SLAPD tools
28 file consists of a series of global configuration options that apply to
30 as a whole (including all backends), followed by zero or more database
31 backend definitions that contain information specific to a backend
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. Blank lines and comment lines beginning with
56 a `#' character are ignored. (Note: continuation lines are unwrapped
57 before comment processing is applied.)
59 Arguments on configuration lines are separated by white space. If an
60 argument contains white space, the argument should be enclosed in
61 double quotes. If an argument contains a double quote (`"') or a
62 backslash character (`\\'), the character should be preceded by a
65 The specific configuration options available are discussed below in the
66 Global Configuration Options, General Backend Options, and General Database
67 Options. Backend-specific options are discussed in the
69 manual pages. Refer to the "OpenLDAP Administrator's Guide" for more
70 details on the slapd configuration file.
71 .SH GLOBAL CONFIGURATION OPTIONS
72 Options described in this section apply to all backends, unless specifically
73 overridden in a backend definition. Arguments that should be replaced by
74 actual text are shown in brackets <>.
76 .B access to <what> "[ by <who> <access> <control> ]+"
77 Grant access (specified by <access>) to a set of entries and/or
78 attributes (specified by <what>) by one or more requestors (specified
82 and the "OpenLDAP's Administrator's Guide" for details.
85 Specify a set of features (separated by white space) to
88 allows acceptance of LDAPv2 bind requests. Note that
90 does not truly implement LDAPv2 (RFC 1777), now Historic (RFC 3494).
92 allows anonymous bind when credentials are not empty (e.g.
95 allows unauthenticated (anonymous) bind when DN is not empty.
97 allow unauthenticated (anonymous) update operations to be processed
98 (subject to access controls and other administrative limits).
100 .B argsfile <filename>
101 The ( absolute ) name of a file that will hold the
103 server's command line options
104 if started without the debugging command line option.
106 .B attributeoptions [option-name]...
107 Define tagging attribute options or option tag/range prefixes.
108 Options must not end with `-', prefixes must end with `-'.
109 The `lang-' prefix is predefined.
112 directive, `lang-' will no longer be defined and you must specify it
113 explicitly if you want it defined.
115 An attribute description with a tagging option is a subtype of that
116 attribute description without the option.
117 Except for that, options defined this way have no special semantics.
118 Prefixes defined this way work like the `lang-' options:
119 They define a prefix for tagging options starting with the prefix.
120 That is, if you define the prefix `x-foo-', you can use the option
122 Furthermore, in a search or compare, a prefix or range name (with
123 a trailing `-') matches all options starting with that name, as well
124 as the option with the range name sans the trailing `-'.
125 That is, `x-foo-bar-' matches `x-foo-bar' and `x-foo-bar-baz'.
127 RFC 2251 reserves options beginning with `x-' for private experiments.
128 Other options should be registered with IANA, see RFC 3383 section 3.4.
129 OpenLDAP also has the `binary' option built in, but this is a transfer
130 option, not a tagging option.
133 .B attributetype "(\ <oid>\
135 [DESC\ <description>]\
144 [NO\-USER\-MODIFICATION]\
145 [USAGE\ <attributeUsage>]\ )"
147 Specify an attribute type using the LDAPv3 syntax defined in RFC 2252.
148 The slapd parser extends the RFC 2252 definition by allowing string
149 forms as well as numeric OIDs to be used for the attribute OID and
150 attribute syntax OID.
156 .B authz-policy <policy>
157 Used to specify which rules to use for Proxy Authorization. Proxy
158 authorization allows a client to authenticate to the server using one
159 user's credentials, but specify a different identity to use for authorization
160 and access control purposes. It essentially allows user A to login as user
161 B, using user A's password.
164 flag disables proxy authorization. This is the default setting.
167 flag will use rules in the
169 attribute of the authorization DN.
172 flag will use rules in the
174 attribute of the authentication DN.
177 flag, an alias for the deprecated value of
179 will allow any of the above, whatever succeeds first (checked in
185 flag requires both authorizations to succeed.
188 The rules are mechanisms to specify which identities are allowed
189 to perform proxy authorization.
192 attribute in an entry specifies which other users
193 are allowed to proxy login to this entry. The
196 an entry specifies which other users this user can authorize as. Use of
199 abused if users are allowed to write arbitrary values to this attribute.
202 attribute must be protected with ACLs such that
203 only privileged users can modify it.
210 or a set of identities; it can take three forms:
213 .B ldap:///<base>??[<scope>]?<filter>
216 .B dn[.<dnstyle>]:<pattern>
219 .B u[<mech>[<realm>]]:<pattern>
222 .B group[/objectClass[/attributeType]]:<pattern>
229 .B <dnstyle>:={exact|onelevel|children|subtree|regex}
232 The first form is a valid LDAP
240 portions must be absent, so that the search occurs locally on either
246 with the optional style modifiers
252 for exact, onelevel, children and subtree matches, which cause
254 to be normalized according to the DN normalization rules, or the special
258 to be compiled according to
262 means any non-anonymous DN.
263 The third form is a SASL
265 with the optional fields
269 that allow to specify a SASL
271 and eventually a SASL
273 for those mechanisms that support one.
274 The need to allow the specification of a mechanism is still debated,
275 and users are strongly discouraged to rely on this possibility.
276 The fourth form is a group specification, consisting of the keyword
278 optionally followed by the specification of the group
284 is searched with base scope, and in case of match, the values of the
287 are searched for the asserted DN.
288 For backwards compatibility, if no identity type is provided, i.e. only
292 is assumed; as a consequence,
294 is subjected to DN normalization.
295 Since the interpretation of
299 can impact security, users are strongly encouraged
300 to explicitly set the type of identity specification that is being used.
301 A subset of these rules can be used as third arg in the
303 statement (see below); significantly, the
310 .B authz-regexp <match> <replace>
311 Used by the authentication framework to convert simple user names,
312 such as provided by SASL subsystem, to an LDAP DN used for
313 authorization purposes. Note that the resultant DN need not refer
314 to an existing entry to be considered valid. When an authorization
315 request is received from the SASL subsystem, the SASL
320 are taken, when available, and combined into a name of the form
324 .B UID=<username>[[,CN=<realm>],CN=<mechanism>],CN=auth
327 This name is then compared against the
329 regular expression, and if the match is successful, the name is
332 string. If there are wildcard strings in the
334 regular expression that are enclosed in parenthesis, e.g.
340 then the portion of the name that matched the wildcard will be stored
341 in the numbered placeholder variable $1. If there are other wildcard strings
342 in parenthesis, the matching strings will be in $2, $3, etc. up to $9. The
343 placeholders can then be used in the
348 .B UID=$1,OU=Accounts,DC=example,DC=com
351 The replaced name can be either a DN or an LDAP URI. If the
352 latter, the server will use the URI to search its own database(s)
353 and, if the search returns exactly one entry, the name is
354 replaced by the DN of that entry. The LDAP URI must have no
355 hostport, attrs, or extensions components, e.g.
358 .B ldap:///OU=Accounts,DC=example,DC=com??one?(UID=$1)
363 options can be given in the configuration file to allow for multiple matching
364 and replacement patterns. The matching patterns are checked in the order they
365 appear in the file, stopping at the first successful match.
368 .\"Because the plus sign + is a character recognized by the regular expression engine,
369 .\"and it will appear in names that include a REALM, be careful to escape the
370 .\"plus sign with a backslash \\+ to remove the character's special meaning.
373 .B concurrency <integer>
374 Specify a desired level of concurrency. Provided to the underlying
375 thread system as a hint. The default is not to provide any hint.
377 .B conn_max_pending <integer>
378 Specify the maximum number of pending requests for an anonymous session.
379 If requests are submitted faster than the server can process them, they
380 will be queued up to this limit. If the limit is exceeded, the session
381 is closed. The default is 100.
383 .B conn_max_pending_auth <integer>
384 Specify the maximum number of pending requests for an authenticated session.
386 .\"-- NEW_LOGGING option --
388 .\".B debug <subsys> <level>
389 .\"Specify a logging level for a particular subsystem. The subsystems include
391 .\"a global level for all subsystems,
395 .\"the backend databases,
397 .\"the entry cache manager,
399 .\"the config file reader,
401 .\"the connection manager,
403 .\"the Cyrus SASL library interface,
405 .\"the search filter processor,
407 .\"the DN normalization library,
409 .\"the database indexer,
411 .\"the ASN.1 BER library,
413 .\"the dynamic module loader,
415 .\"the LDAP operation processors,
417 .\"the SASL authentication subsystem,
419 .\"the schema processor, and
421 .\"the TLS library interface. This is not an exhaustive list; there are many
422 .\"other subsystems and more are added over time.
424 .\"The levels are, in order of decreasing priority:
425 .\".B emergency, alert, critical, error, warning, notice, information, entry,
426 .\".B args, results, detail1, detail2
427 .\"An integer may be used instead, with 0 corresponding to
433 .\"level logs function entry points,
435 .\"adds function call parameters, and
437 .\"adds the function results to the logs.
442 .\"levels add even more low level detail from individual functions.
444 .B defaultsearchbase <dn>
445 Specify a default search base to use when client submits a
446 non-base search request with an empty base DN.
448 .B disallow <features>
449 Specify a set of features (separated by white space) to
450 disallow (default none).
452 disables acceptance of anonymous bind requests.
454 disables simple (bind) authentication.
456 disables Kerberos V4 (bind) authentication.
458 disables Start TLS from forcing session to anonymous status (see also
461 disables StartTLS if authenticated (see also
465 .B ditcontentrule "(\ <oid>\
467 [DESC\ <description>]\
474 Specify an DIT Content Rule using the LDAPv3 syntax defined in RFC 2252.
475 The slapd parser extends the RFC 2252 definition by allowing string
476 forms as well as numeric OIDs to be used for the attribute OID and
477 attribute syntax OID.
483 .B gentlehup { on | off }
484 A SIGHUP signal will only cause a 'gentle' shutdown-attempt:
486 will stop listening for new connections, but will not close the
487 connections to the current clients. Future write operations return
488 unwilling-to-perform, though. Slapd terminates when all clients
489 have closed their connections (if they ever do), or \- as before \-
490 if it receives a SIGTERM signal. This can be useful if you wish to
491 terminate the server and start a new
494 .B with another database,
495 without disrupting the currently active clients.
496 The default is off. You may wish to use
498 along with this option.
500 .B idletimeout <integer>
501 Specify the number of seconds to wait before forcibly closing
502 an idle client connection. A idletimeout of 0 disables this
503 feature. The default is 0.
505 .B include <filename>
506 Read additional configuration information from the given file before
507 continuing with the next line of the current file.
508 .\"-- NEW_LOGGING option --
510 .\".B logfile <filename>
511 .\"Specify a file for recording debug log messages. By default these messages
512 .\"only go to stderr and are not recorded anywhere else. Specifying a logfile
513 .\"copies messages to both stderr and the logfile.
516 Specifies the Security Strength Factor (SSF) to be given local LDAP sessions,
517 such as those to the ldapi:// listener. For a description of SSF values,
521 option description. The default is 71.
523 .B loglevel <integer> [...]
524 Specify the level at which debugging statements and operation
525 statistics should be syslogged (currently logged to the
527 LOG_LOCAL4 facility). Log levels are additive, and available levels
539 debug packet handling
543 heavy trace debugging
547 connection management
551 print out packets sent and received
555 search filter processing
559 configuration file processing
563 access control list processing
567 stats log connections/operations/results
571 stats log entries sent
575 print communication with shell backends
582 The desired log level can be input as a single integer that combines
583 the (ORed) desired levels, as a list of integers (that are ORed internally),
584 or as a list of the names that are shown between brackets, such that
595 can be used as a shortcut to enable logging at all levels (equivalent to -1).
598 .B moduleload <filename>
599 Specify the name of a dynamically loadable module to load. The filename
600 may be an absolute path name or a simple filename. Non-absolute names
601 are searched for in the directories specified by the
603 option. This option and the
605 option are only usable if slapd was compiled with --enable-modules.
607 .B modulepath <pathspec>
608 Specify a list of directories to search for loadable modules. Typically
609 the path is colon-separated but this depends on the operating system.
612 .B objectclass "(\ <oid>\
614 [DESC\ <description]\
617 [{ ABSTRACT | STRUCTURAL | AUXILIARY }]\
618 [MUST\ <oids>] [MAY\ <oids>] )"
620 Specify an objectclass using the LDAPv3 syntax defined in RFC 2252.
621 The slapd parser extends the RFC 2252 definition by allowing string
622 forms as well as numeric OIDs to be used for the object class OID.
626 description.) Object classes are "STRUCTURAL" by default.
629 .B objectidentifier <name> "{ <oid> | <name>[:<suffix>] }"
630 Define a string name that equates to the given OID. The string can be used
631 in place of the numeric OID in objectclass and attribute definitions. The
632 name can also be used with a suffix of the form ":xx" in which case the
633 value "oid.xx" will be used.
635 .B password-hash <hash> [<hash>...]
636 This option configures one or more hashes to be used in generation of user
637 passwords stored in the userPassword attribute during processing of
638 LDAP Password Modify Extended Operations (RFC 3062).
639 The <hash> must be one of
653 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
658 use the MD5 algorithm (RFC 1321), the latter with a seed.
665 indicates that the new password should be
666 added to userPassword as clear text.
668 Note that this option does not alter the normal user applications
669 handling of userPassword during LDAP Add, Modify, or other LDAP operations.
671 .B password\-crypt\-salt\-format <format>
672 Specify the format of the salt passed to
674 when generating {CRYPT} passwords (see
676 during processing of LDAP Password Modify Extended Operations (RFC 3062).
678 This string needs to be in
680 format and may include one (and only one) %s conversion.
681 This conversion will be substituted with a string of random
682 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
683 provides a two character salt and "$1$%.8s" tells some
684 versions of crypt(3) to use an MD5 algorithm and provides
685 8 random characters of salt. The default is "%s", which
686 provides 31 characters of salt.
688 .B pidfile <filename>
689 The ( absolute ) name of a file that will hold the
691 server's process ID ( see
693 ) if started without the debugging command line option.
696 Specify the referral to pass back when
698 cannot find a local database to handle a request.
699 If specified multiple times, each url is provided.
702 The ( absolute ) name of a file that will hold the
704 server's command line options
705 if started without the debugging command line option.
708 The ( absolute ) name of a file that will hold the
710 server's process ID ( see
712 ) if started without the debugging command line option.
714 .B replicationinterval
715 The number of seconds
717 waits before checking the replogfile for changes.
719 .B require <conditions>
720 Specify a set of conditions (separated by white space) to
721 require (default none).
722 The directive may be specified globally and/or per-database.
724 requires bind operation prior to directory operations.
726 requires session to be using LDAP version 3.
728 requires authentication prior to directory operations.
730 requires SASL authentication prior to directory operations.
732 requires strong authentication prior to directory operations.
733 The strong keyword allows protected "simple" authentication
734 as well as SASL authentication.
736 may be used to require no conditions (useful for clearly globally
737 set conditions within a particular database).
739 .B reverse-lookup on | off
740 Enable/disable client name unverified reverse lookup (default is
742 if compiled with --enable-rlookups).
745 Specify the name of an LDIF(5) file containing user defined attributes
746 for the root DSE. These attributes are returned in addition to the
747 attributes normally produced by slapd.
750 Used to specify the fully qualified domain name used for SASL processing.
752 .B sasl-realm <realm>
753 Specify SASL realm. Default is empty.
755 .B sasl-secprops <properties>
756 Used to specify Cyrus SASL security properties.
759 flag (without any other properties) causes the flag properties
760 default, "noanonymous,noplain", to be cleared.
763 flag disables mechanisms susceptible to simple passive attacks.
766 flag disables mechanisms susceptible to active attacks.
769 flag disables mechanisms susceptible to passive dictionary attacks.
772 flag disables mechanisms which support anonymous login.
775 flag require forward secrecy between sessions.
778 require mechanisms which pass client credentials (and allow
779 mechanisms which can pass credentials to do so).
782 property specifies the minimum acceptable
783 .I security strength factor
784 as an integer approximate to effective key length used for
785 encryption. 0 (zero) implies no protection, 1 implies integrity
786 protection only, 56 allows DES or other weak ciphers, 112
787 allows triple DES and other strong ciphers, 128 allows RC4,
788 Blowfish and other modern strong ciphers. The default is 0.
791 property specifies the maximum acceptable
792 .I security strength factor
793 as an integer (see minssf description). The default is INT_MAX.
796 property specifies the maximum security layer receive buffer
797 size allowed. 0 disables security layers. The default is 65536.
800 Specify the distinguished name for the subschema subentry that
801 controls the entries on this server. The default is "cn=Subschema".
803 .B security <factors>
804 Specify a set of security strength factors (separated by white space)
808 option for a description of security strength factors).
809 The directive may be specified globally and/or per-database.
811 specifies the overall security strength factor.
813 specifies the transport security strength factor.
815 specifies the TLS security strength factor.
817 specifies the SASL security strength factor.
819 specifies the overall security strength factor to require for
821 .B update_transport=<n>
822 specifies the transport security strength factor to require for
825 specifies the TLS security strength factor to require for
828 specifies the SASL security strength factor to require for
831 specifies the security strength factor required for
833 username/password authentication.
836 factor is measure of security provided by the underlying transport,
837 e.g. ldapi:// (and eventually IPSEC). It is not normally used.
839 .B sizelimit {<integer>|unlimited}
841 .B sizelimit size[.{soft|hard|unchecked}]=<integer> [...]
842 Specify the maximum number of entries to return from a search operation.
843 The default size limit is 500.
846 to specify no limits.
847 The second format allows a fine grain setting of the size limits.
848 Extra args can be added on the same line.
851 for an explanation of the different flags.
853 .B sockbuf_max_incoming <integer>
854 Specify the maximum incoming LDAP PDU size for anonymous sessions.
855 The default is 262143.
857 .B sockbuf_max_incoming_auth <integer>
858 Specify the maximum incoming LDAP PDU size for authenticated sessions.
859 The default is 4194303.
862 Specify the srvtab file in which the kerberos keys necessary for
863 authenticating clients using kerberos can be found. This option is only
864 meaningful if you are using Kerberos authentication.
867 Specify the maximum size of the primary thread pool.
870 .B timelimit {<integer>|unlimited}
872 .B timelimit time[.{soft|hard}]=<integer> [...]
873 Specify the maximum number of seconds (in real time)
875 will spend answering a search request. The default time limit is 3600.
878 to specify no limits.
879 The second format allows a fine grain setting of the time limits.
880 Extra args can be added on the same line.
883 for an explanation of the different flags.
885 .B ucdata-path <path>
886 Specify the path to the directory containing the Unicode character
887 tables. The default path is DATADIR/ucdata.
891 is built with support for Transport Layer Security, there are more options
894 .B TLSCipherSuite <cipher-suite-spec>
895 Permits configuring what ciphers will be accepted and the preference order.
896 <cipher-suite-spec> should be a cipher specification for OpenSSL. Example:
898 TLSCipherSuite HIGH:MEDIUM:+SSLv2
900 To check what ciphers a given spec selects, use:
902 openssl ciphers -v <cipher-suite-spec>
904 .B TLSCACertificateFile <filename>
905 Specifies the file that contains certificates for all of the Certificate
910 .B TLSCACertificatePath <path>
911 Specifies the path of a directory that contains Certificate Authority
912 certificates in separate individual files. Usually only one of this
913 or the TLSCACertificateFile is used.
915 .B TLSCertificateFile <filename>
916 Specifies the file that contains the
920 .B TLSCertificateKeyFile <filename>
921 Specifies the file that contains the
923 server private key that matches the certificate stored in the
924 .B TLSCertificateFile
925 file. Currently, the private key must not be protected with a password, so
926 it is of critical importance that it is protected carefully.
928 .B TLSRandFile <filename>
929 Specifies the file to obtain random bits from when /dev/[u]random
930 is not available. Generally set to the name of the EGD/PRNGD socket.
931 The environment variable RANDFILE can also be used to specify the filename.
933 .B TLSVerifyClient <level>
934 Specifies what checks to perform on client certificates in an
935 incoming TLS session, if any.
938 can be specified as one of the following keywords:
944 will not ask the client for a certificate.
947 The client certificate is requested. If no certificate is provided,
948 the session proceeds normally. If a bad certificate is provided,
949 it will be ignored and the session proceeds normally.
952 The client certificate is requested. If no certificate is provided,
953 the session proceeds normally. If a bad certificate is provided,
954 the session is immediately terminated.
956 .B demand | hard | true
957 These keywords are all equivalent, for compatibility reasons.
958 The client certificate is requested. If no certificate is provided,
959 or a bad certificate is provided, the session is immediately terminated.
961 Note that a valid client certificate is required in order to use the
962 SASL EXTERNAL authentication mechanism with a TLS session. As such,
965 setting must be chosen to enable SASL EXTERNAL authentication.
967 .SH GENERAL BACKEND OPTIONS
968 Options in this section only apply to the configuration file section
969 for the specified backend. They are supported by every
972 .B backend <databasetype>
973 Mark the beginning of a backend definition. <databasetype>
989 depending on which backend will serve the database.
991 .SH GENERAL DATABASE OPTIONS
992 Options in this section only apply to the configuration file section
993 for the database in which they are defined. They are supported by every
994 type of backend. Note that the
998 option are mandatory for each database.
1000 .B database <databasetype>
1001 Mark the beginning of a new database instance definition. <databasetype>
1017 depending on which backend will serve the database.
1022 will automatically maintain the
1023 modifiersName, modifyTimestamp, creatorsName, and
1024 createTimestamp attributes for entries. By default, lastmod is on.
1026 .B limits <who> <limit> [<limit> [...]]
1027 Specify time and size limits based on who initiated an operation.
1034 anonymous | users | [dn[.<style>]=]<pattern> | group[/oc[/at]]=<pattern>
1040 <style> ::= exact | base | onelevel | subtree | children | regex | anonymous
1045 matches all unauthenticated clients.
1048 matches all authenticated clients;
1051 dn pattern is assumed unless otherwise specified by qualifying
1052 the (optional) key string
1058 (which are synonyms), to require an exact match; with
1060 to require exactly one level of depth match; with
1062 to allow any level of depth match, including the exact match; with
1064 to allow any level of depth match, not including the exact match;
1066 explicitly requires the (default) match based on regular expression
1067 pattern, as detailed in
1071 matches unbound operations; the
1074 The same behavior is obtained by using the
1081 with the optional objectClass
1087 sets the limits for any DN listed in the values of the
1093 group objectClass (default
1095 whose DN exactly matches
1098 The currently supported limits are
1103 The syntax for time limits is
1104 .BR time[.{soft|hard}]=<integer> ,
1107 is the number of seconds slapd will spend answering a search request.
1108 If no time limit is explicitly requested by the client, the
1110 limit is used; if the requested time limit exceeds the
1113 .\".I "Administrative limit exceeded"
1114 .\"error is returned.
1115 limit, the value of the limit is used instead.
1118 limit is set to the keyword
1120 the soft limit is used in either case; if it is set to the keyword
1122 no hard limit is enforced.
1123 Explicit requests for time limits smaller or equal to the
1126 If no limit specifier is set, the value is assigned to the
1132 to preserve the original behavior.
1134 The syntax for size limits is
1135 .BR size[.{soft|hard|unchecked}]=<integer> ,
1138 is the maximum number of entries slapd will return answering a search
1140 If no size limit is explicitly requested by the client, the
1142 limit is used; if the requested size limit exceeds the
1145 .\".I "Administrative limit exceeded"
1146 .\"error is returned.
1147 limit, the value of the limit is used instead.
1150 limit is set to the keyword
1152 the soft limit is used in either case; if it is set to the keyword
1154 no hard limit is enforced.
1155 Explicit requests for size limits smaller or equal to the
1160 specifier sets a limit on the number of candidates a search request is allowed
1162 The rationale behind it is that searches for non-properly indicized
1163 attributes may result in large sets of candidates, which must be
1166 to determine whether they match the search filter or not.
1169 limit provides a means to drop such operations before they are even
1171 If the selected candidates exceed the
1173 limit, the search will abort with
1174 .IR "Unwilling to perform" .
1175 If it is set to the keyword
1177 no limit is applied (the default).
1180 the search is not even performed; this can be used to disallow searches
1181 for a specific set of users.
1182 If no limit specifier is set, the value is assigned to the
1188 to preserve the original behavior.
1190 In case of no match, the global limits are used.
1191 The default values are the same of
1200 control is requested, the
1202 size limit is used by default, because the request of a specific page size
1203 is considered an explicit request for a limitation on the number
1204 of entries to be returned.
1205 However, the size limit applies to the total count of entries returned within
1206 the search, and not to a single page.
1207 Additional size limits may be enforced; the syntax is
1208 .BR size.pr={<integer>|noEstimate|unlimited} ,
1211 is the max page size if no explicit limit is set; the keyword
1213 inhibits the server from returning an estimate of the total number
1214 of entries that might be returned
1215 (note: the current implementation does not return any estimate).
1218 indicates that no limit is applied to the pagedResults control page size.
1220 .B size.prtotal={<integer>|unlimited|disabled}
1221 allows to set a limit on the total number of entries that a pagedResults
1222 control allows to return.
1223 By default it is set to the
1228 is the max number of entries that the whole search with pagedResults control
1232 to allow unlimited number of entries to be returned, e.g. to allow
1233 the use of the pagedResults control as a means to circumvent size
1234 limitations on regular searches; the keyword
1236 disables the control, i.e. no paged results can be returned.
1237 Note that the total number of entries returned when the pagedResults control
1238 is requested cannot exceed the
1240 size limit of regular searches unless extended by the
1245 .B maxderefdepth <depth>
1246 Specifies the maximum number of aliases to dereference when trying to
1247 resolve an entry, used to avoid infinite alias loops. The default is 1.
1249 .B overlay <overlay-name>
1250 Add the specified overlay to this database. An overlay is a piece of
1251 code that intercepts database operations in order to extend or change
1252 them. Overlays are pushed onto
1253 a stack over the database, and so they will execute in the reverse
1254 of the order in which they were configured and the database itself
1255 will receive control last of all.
1257 .B readonly on | off
1258 This option puts the database into "read-only" mode. Any attempts to
1259 modify the database will return an "unwilling to perform" error. By
1260 default, readonly is off.
1263 .B replica uri=ldap[s]://<hostname>[:port]|host=<hostname>[:port]
1264 .B [starttls=yes|critical]
1265 .B [suffix=<suffix> [...]]
1266 .B bindmethod=simple|sasl [binddn=<simple DN>] [credentials=<simple password>]
1267 .B [saslmech=<SASL mech>] [secprops=<properties>] [realm=<realm>]
1268 .B [authcId=<authentication ID>] [authzId=<authorization ID>]
1269 .B [attr[!]=<attr list>]
1271 Specify a replication site for this database. Refer to the "OpenLDAP
1272 Administrator's Guide" for detailed information on setting up a replicated
1274 directory service. Zero or more
1276 instances can be used to select the subtrees that will be replicated
1277 (defaults to all the database).
1279 is deprecated in favor of the
1283 allows the replica LDAP server to be specified as an LDAP URI.
1288 requires the options
1292 and should only be used when adequate security services
1293 (e.g TLS or IPSEC) are in place. A
1299 Specific security properties (as with the
1301 keyword above) for a SASL bind can be set with the
1303 option. A non-default SASL realm can be set with the
1308 will use Kerberos, a kerberos instance should be given in
1312 can be given after the
1314 keyword to allow the selective replication of the listed attributes only;
1317 mark is used, the list is considered exclusive, i.e. the listed attributes
1319 If an objectClass is listed, all the related attributes
1320 are (are not) replicated.
1323 .B replogfile <filename>
1324 Specify the name of the replication log file to log changes to.
1325 The replication log is typically written by
1330 .BR slapd.replog (5)
1331 for more information. The specified file should be located
1332 in a directory with limited read/write/execute access as the replication
1333 logs may contain sensitive information.
1335 .B restrict <oplist>
1336 Specify a whitespace separated list of operations that are restricted.
1337 If defined inside a database specification, restrictions apply only
1338 to that database, otherwise they are global.
1339 Operations can be any of
1344 .BR extended[=<OID>] ,
1348 or the special pseudo-operations
1352 which respectively summarize read and write operations.
1360 keyword allows to indicate the OID of the specific operation
1364 Specify the distinguished name that is not subject to access control
1365 or administrative limit restrictions for operations on this database.
1366 This DN may or may not be associated with an entry. An empty root
1367 DN (the default) specifies no root access is to be granted. It is
1368 recommended that the rootdn only be specified when needed (such as
1369 when initially populating a database). If the rootdn is within
1370 a namingContext (suffix) of the database, a simple bind password
1371 may also be provided using the
1375 .B rootpw <password>
1376 Specify a password (or hash of the password) for the rootdn. The
1377 password can only be set if the rootdn is within the namingContext
1378 (suffix) of the database.
1379 This option accepts all RFC 2307 userPassword formats known to
1382 description) as well as cleartext.
1384 may be used to generate a hash of a password. Cleartext
1385 and \fB{CRYPT}\fP passwords are not recommended. If empty
1386 (the default), authentication of the root DN is by other means
1387 (e.g. SASL). Use of SASL is encouraged.
1389 .B suffix <dn suffix>
1390 Specify the DN suffix of queries that will be passed to this
1391 backend database. Multiple suffix lines can be given and at least one is
1392 required for each database definition.
1393 If the suffix of one database is "inside" that of another, the database
1394 with the inner suffix must come first in the configuration file.
1397 Specify that the current backend database is a subordinate of another
1398 backend database. A subordinate database may have only one suffix. This
1399 option may be used to glue multiple databases into a single namingContext.
1400 If the suffix of the current database is within the namingContext of a
1401 superior database, searches against the superior database will be
1402 propagated to the subordinate as well. All of the databases
1403 associated with a single namingContext should have identical rootdns.
1404 Behavior of other LDAP operations is unaffected by this setting. In
1405 particular, it is not possible to use moddn to move an entry from
1406 one subordinate to another subordinate within the namingContext.
1409 .B syncrepl rid=<replica ID>
1410 .B provider=ldap[s]://<hostname>[:port]
1411 .B [type=refreshOnly|refreshAndPersist]
1412 .B [interval=dd:hh:mm:ss]
1413 .B [searchbase=<base DN>]
1414 .B [filter=<filter str>]
1415 .B [scope=sub|one|base]
1416 .B [attrs=<attr list>]
1418 .B [sizelimit=<limit>]
1419 .B [timelimit=<limit>]
1420 .B [schemachecking=on|off]
1422 .B [bindmethod=simple|sasl]
1424 .B [saslmech=<mech>]
1425 .B [authcid=<identity>]
1426 .B [authzid=<identity>]
1427 .B [credentials=<passwd>]
1429 .B [secprops=<properties>]
1431 Specify the current database as a replica which is kept up-to-date with the
1432 master content by establishing the current
1434 as a replication consumer site running a
1437 The replica content is kept synchronized to the master content using
1438 the LDAP Content Synchronization protocol. Refer to the
1439 "OpenLDAP Administrator's Guide" for detailed information on
1440 setting up a replicated
1442 directory service using the
1446 identifies the current
1448 directive within the replication consumer site.
1449 It is a non-negative integer having no more than three digits.
1451 specifies the replication provider site containing the master content
1452 as an LDAP URI. If <port> is not given, the standard LDAP port number
1453 (389 or 636) is used. The content of the
1455 replica is defined using a search
1456 specification as its result set. The consumer
1458 will send search requests to the provider
1460 according to the search specification. The search specification includes
1461 .B searchbase, scope, filter, attrs, attrsonly, sizelimit,
1464 parameters as in the normal search specification.
1465 The search specification for the LDAP Content Synchronization operation
1466 has the same value syntax and the same default values as in the
1469 The LDAP Content Synchronization protocol has two operation types.
1472 operation, the next synchronization search operation
1473 is periodically rescheduled at an interval time (specified by
1475 parameter; 1 day by default)
1476 after each synchronization operation finishes.
1478 .B refreshAndPersist
1479 operation, a synchronization search remains persistent in the provider slapd.
1480 Further updates to the master replica will generate
1481 .B searchResultEntry
1482 to the consumer slapd as the search responses to the persistent
1483 synchronization search. If the connection is lost, the consumer will
1484 attempt to reconnect at an interval time (specified by
1486 parameter; 60 seconds by default) until the session is re-established.
1487 The schema checking can be enforced at the LDAP Sync
1488 consumer site by turning on the
1490 parameter. The default is off.
1493 parameter specifies the DN in the consumer site
1494 which is allowed to make changes to the replica.
1495 The DN should have read/write access to the replica database.
1500 of the master database.
1505 requires the options
1509 and should only be used when adequate security services
1510 (e.g. TLS or IPSEC) are in place.
1517 Depending on the mechanism, an authentication identity and/or
1518 credentials can be specified using
1524 parameter may be used to specify an authorization identity.
1525 Specific security properties (as with the
1527 keyword above) for a SASL bind can be set with the
1529 option. A non default SASL realm can be set with the
1535 This option is only applicable in a slave
1536 database updated using
1538 It specifies the DN permitted to update (subject to access controls)
1539 the replica (typically, this is the DN
1541 binds to update the replica). Generally, this DN
1548 Specify the referral to pass back when
1550 is asked to modify a replicated local database.
1551 If specified multiple times, each url is provided.
1553 .SH DATABASE-SPECIFIC OPTIONS
1554 Each database may allow specific configuration options; they are
1555 documented separately in the backends' manual pages.
1557 The following backends can be compiled into slapd.
1558 They are documented in the
1559 .BR slapd-<backend> (5)
1563 This is the recommended backend for a normal slapd database.
1564 However, it takes more care than with the LDBM backend to configure
1566 It uses the Sleepycat Berkeley DB (BDB) package to store data.
1569 This is the database backend which is easiest to configure.
1570 However, it does not offer the data durability features of the BDB
1572 It uses Berkeley DB or GDBM to store data.
1575 This backend is experimental.
1576 It serves up referrals based upon SRV resource records held in the
1580 This backend acts as a proxy to forward incoming requests to another
1584 This backend performs basic LDAP proxying with respect to a set of
1585 remote LDAP servers. It is an enhancement of the ldap backend. The
1586 proxy cache extension of meta backend provides answering of search
1587 requests from the proxy using results of previously cached requests.
1590 This backend provides information about the running status of the slapd
1594 Operations in this backend succeed but do nothing.
1597 This backend is provided for demonstration purposes only.
1598 It serves up user account information from the system
1603 This backend embeds a
1605 interpreter into slapd.
1606 It runs Perl subroutines to implement LDAP operations.
1609 This backend redirects LDAP operations to another database
1610 in the same server, based on the naming context of the request.
1611 Its use requires the
1615 for details) to rewrite the naming context of the request.
1616 It is is primarily intended to implement virtual views on databases
1617 that actually store data.
1620 This backend executes external programs to implement LDAP operations.
1621 It is primarily intended to be used in prototypes.
1624 This backend is experimental.
1625 It services LDAP requests from an SQL database.
1628 This backend is experimental.
1631 interpreter into slapd.
1632 It runs Tcl commands to implement LDAP operations.
1635 Here is a short example of a configuration file:
1639 include SYSCONFDIR/schema/core.schema
1640 pidfile LOCALSTATEDIR/slapd.pid
1642 # Subtypes of "name" (e.g. "cn" and "ou") with the
1643 # option ";x-hidden" can be searched for/compared,
1644 # but are not shown. See \fBslapd.access\fP(5).
1645 attributeoptions x-hidden lang-
1646 access to attr=name;x-hidden by * =cs
1649 suffix "dc=our-domain,dc=com"
1650 # The database directory MUST exist prior to
1651 # running slapd AND should only be accessible
1652 # by the slapd/tools. Mode 0700 recommended.
1653 directory LOCALSTATEDIR/openldap-data
1654 # Indices to maintain
1655 index objectClass eq
1656 index cn,sn,mail pres,eq,approx,sub
1658 # We serve small clients that do not handle referrals,
1659 # so handle remote lookups on their behalf.
1662 uri ldap://ldap.some-server.com/
1667 "OpenLDAP Administrator's Guide" contains a longer annotated
1668 example of a configuration file.
1669 The original ETCDIR/slapd.conf is another example.
1673 default slapd configuration file
1677 .BR slapd\-dnssrv (5),
1678 .BR slapd\-ldap (5),
1679 .BR slapd\-ldbm (5),
1680 .BR slapd\-meta (5),
1681 .BR slapd\-monitor (5),
1682 .BR slapd\-null (5),
1683 .BR slapd\-passwd (5),
1684 .BR slapd\-perl (5),
1685 .BR slapd\-relay (5),
1686 .BR slapd\-shell (5),
1689 .BR slapd.access (5),
1690 .BR slapd.plugin (5),
1691 .BR slapd.replog (5),
1703 Known overlays are documented in
1704 .BR slapo\-lastmod (5),
1705 .BR slapo\-pcache (5),
1706 .BR slapo\-ppolicy (5),
1707 .BR slapo\-refint (5),
1709 .BR slapo\-unique (5).
1711 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
1712 .SH ACKNOWLEDGEMENTS
1714 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
1716 is derived from University of Michigan LDAP 3.3 Release.
projects / openldap / blob