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
24 file consists of a series of global configuration options that apply to
26 as a whole (including all backends), followed by zero or more database
27 backend definitions that contain information specific to a backend
35 # comment - these options apply to every database
36 <global configuration options>
37 # first database definition & configuration options
38 database <backend 1 type>
39 <configuration options specific to backend 1>
40 # subsequent database definitions & configuration options
44 As many backend-specific sections as desired may be included. Global
45 options can be overridden in a backend (for options that appear more
46 than once, the last appearance in the
50 If a line begins with white space, it is considered a continuation
51 of the previous line. Blank lines and comment lines beginning with
52 a `#' character are ignored. (Note: continuation lines are unwrapped
53 before comment processing is applied.)
55 Arguments on configuration lines are separated by white space. If an
56 argument contains white space, the argument should be enclosed in
57 double quotes. If an argument contains a double quote (`"') or a
58 backslash character (`\\'), the character should be preceded by a
61 The specific configuration options available are discussed below in the
62 Global Configuration Options, General Backend Options, and General Database
63 Options. Backend-specific options are discussed in the
65 manual pages. Refer to the "OpenLDAP Administrator's Guide" for more
66 details on the slapd configuration file.
67 .SH GLOBAL CONFIGURATION OPTIONS
68 Options described in this section apply to all backends, unless specifically
69 overridden in a backend definition. Arguments that should be replaced by
70 actual text are shown in brackets <>.
72 .B access to <what> "[ by <who> <access> <control> ]+"
73 Grant access (specified by <access>) to a set of entries and/or
74 attributes (specified by <what>) by one or more requestors (specified
78 and the "OpenLDAP's Administrator's Guide" for details.
81 Specify a set of features (separated by white space) to
84 allows acceptance of LDAPv2 bind requests. Note that
86 does not truly implement LDAPv2 (RFC 1777), now Historic (RFC 3494).
88 allows anonymous bind when credentials are not empty (e.g.
91 allows unauthenticated (anonymous) bind when DN is not empty.
93 allow unauthenticated (anonymous) update operations to be processed
94 (subject to access controls and other administrative limits).
96 .B argsfile <filename>
97 The ( absolute ) name of a file that will hold the
99 server's command line options
100 if started without the debugging command line option.
102 .B attributeoptions [option-name]...
103 Define tagging attribute options or option tag/range prefixes.
104 Options must not end with `-', prefixes must end with `-'.
105 The `lang-' prefix is predefined.
108 directive, `lang-' will no longer be defined and you must specify it
109 explicitly if you want it defined.
111 An attribute description with a tagging option is a subtype of that
112 attribute description without the option.
113 Except for that, options defined this way have no special semantics.
114 Prefixes defined this way work like the `lang-' options:
115 They define a prefix for tagging options starting with the prefix.
116 That is, if you define the prefix `x-foo-', you can use the option
118 Furthermore, in a search or compare, a prefix or range name (with
119 a trailing `-') matches all options starting with that name, as well
120 as the option with the range name sans the trailing `-'.
121 That is, `x-foo-bar-' matches `x-foo-bar' and `x-foo-bar-baz'.
123 RFC 2251 reserves options beginning with `x-' for private experiments.
124 Other options should be registered with IANA, see RFC 3383 section 3.4.
125 OpenLDAP also has the `binary' option built in, but this is a transfer
126 option, not a tagging option.
129 .B attributetype "(\ <oid>\
131 [DESC\ <description>]\
140 [NO\-USER\-MODIFICATION]\
141 [USAGE\ <attributeUsage>]\ )"
143 Specify an attribute type using the LDAPv3 syntax defined in RFC 2252.
144 The slapd parser extends the RFC 2252 definition by allowing string
145 forms as well as numeric OIDs to be used for the attribute OID and
146 attribute syntax OID.
152 .B concurrency <integer>
153 Specify a desired level of concurrency. Provided to the underlying
154 thread system as a hint. The default is not to provide any hint.
156 .B conn_max_pending <integer>
157 Specify the maximum number of pending requests for an anonymous session.
158 If requests are submitted faster than the server can process them, they
159 will be queued up to this limit. If the limit is exceeded, the session
160 is closed. The default is 100.
162 .B conn_max_pending_auth <integer>
163 Specify the maximum number of pending requests for an authenticated session.
166 .\".B debug <subsys> <level>
167 .\"Specify a logging level for a particular subsystem. The subsystems include
169 .\"a global level for all subsystems,
173 .\"the backend databases,
175 .\"the entry cache manager,
177 .\"the config file reader,
179 .\"the connection manager,
181 .\"the Cyrus SASL library interface,
183 .\"the search filter processor,
185 .\"the DN normalization library,
187 .\"the database indexer,
189 .\"the ASN.1 BER library,
191 .\"the dynamic module loader,
193 .\"the LDAP operation processors,
195 .\"the SASL authentication subsystem,
197 .\"the schema processor, and
199 .\"the TLS library interface. This is not an exhaustive list; there are many
200 .\"other subsystems and more are added over time.
202 .\"The levels are, in order of decreasing priority:
203 .\".B emergency, alert, critical, error, warning, notice, information, entry,
204 .\".B args, results, detail1, detail2
205 .\"An integer may be used instead, with 0 corresponding to
211 .\"level logs function entry points,
213 .\"adds function call parameters, and
215 .\"adds the function results to the logs.
220 .\"levels add even more low level detail from individual functions.
222 .B defaultsearchbase <dn>
223 Specify a default search base to use when client submits a
224 non-base search request with an empty base DN.
226 .B disallow <features>
227 Specify a set of features (separated by white space) to
228 disallow (default none).
230 disables acceptance of anonymous bind requests.
232 disables simple (bind) authentication.
234 disables Kerberos V4 (bind) authentication.
236 disables Start TLS from forcing session to anonymous status (see also
239 disables StartTLS if authenticated (see also
243 .B ditcontentrule "(\ <oid>\
245 [DESC\ <description>]\
252 Specify an DIT Content Rule using the LDAPv3 syntax defined in RFC 2252.
253 The slapd parser extends the RFC 2252 definition by allowing string
254 forms as well as numeric OIDs to be used for the attribute OID and
255 attribute syntax OID.
261 .B gentlehup { on | off }
262 A SIGHUP signal will only cause a 'gentle' shutdown-attempt:
264 will stop listening for new connections, but will not close the
265 connections to the current clients. Future write operations return
266 unwilling-to-perform, though. Slapd terminates when all clients
267 have closed their connections (if they ever do), or \- as before \-
268 if it receives a SIGTERM signal. This can be useful if you wish to
269 terminate the server and start a new
272 .B with another database,
273 without disrupting the currently active clients.
274 The default is off. You may wish to use
276 along with this option.
278 .B idletimeout <integer>
279 Specify the number of seconds to wait before forcibly closing
280 an idle client connection. A idletimeout of 0 disables this
281 feature. The default is 0.
283 .B include <filename>
284 Read additional configuration information from the given file before
285 continuing with the next line of the current file.
287 .B limits <who> <limit> [<limit> [...]]
288 Specify time and size limits based on who initiated an operation.
295 anonymous | users | [dn[.<style>]=]<pattern> | group[/oc[/at]]=<pattern>
301 <style> ::= exact | base | onelevel | subtree | children | regex | anonymous
306 matches all unauthenticated clients.
309 matches all authenticated clients;
312 dn pattern is assumed unless otherwise specified by qualifying
313 the (optional) key string
319 (which are synonyms), to require an exact match; with
321 to require exactly one level of depth match; with
323 to allow any level of depth match, including the exact match; with
325 to allow any level of depth match, not including the exact match;
327 explicitly requires the (default) match based on regular expression
328 pattern, as detailed in
332 matches unbound operations; the
335 The same behavior is obtained by using the
342 with the optional objectClass
348 sets the limits for any DN listed in the values of the
354 group objectClass (default
356 whose DN exactly matches
359 The currently supported limits are
364 The syntax for time limits is
365 .BR time[.{soft|hard}]=<integer> ,
368 is the number of seconds slapd will spend answering a search request.
369 If no time limit is explicitly requested by the client, the
371 limit is used; if the requested time limit exceeds the
374 .I \"Administrative limit exceeded\"
378 limit is set to 0 or to the keyword
380 the soft limit is used in either case; if it is set to
384 no hard limit is enforced.
385 Explicit requests for time limits smaller or equal to the
388 If no flag is set, the value is assigned to the
392 limit is set to zero, to preserve the original behavior.
394 The syntax for size limits is
395 .BR size[.{soft|hard|unchecked}]=<integer> ,
398 is the maximum number of entries slapd will return answering a search
400 If no size limit is explicitly requested by the client, the
402 limit is used; if the requested size limit exceeds the
405 .I \"Administrative limit exceeded\"
409 limit is set to 0 or to the keyword
411 the soft limit is used in either case; if it is set to
415 no hard limit is enforced.
416 Explicit requests for size limits smaller or equal to the
421 flag sets a limit on the number of candidates a search request is allowed
423 If the selected candidates exceed the
425 limit, the search will abort with
426 .IR \"Unwilling to perform\" .
431 no limit is applied (the default).
432 If no flag is set, the value is assigned to the
436 limit is set to zero, to preserve the original behavior.
438 In case of no match, the global limits are used.
439 The default values are the same of
448 control is defined, additional size limits may be enforced; the syntax is
449 .BR size.pr={<integer>|noEstimate} ,
452 is the max page size if no explicit limit is set; the keyword
454 inhibits the server to return an estimate of the total number
455 of entries that will be returned.
458 .\".B logfile <filename>
459 .\"Specify a file for recording debug log messages. By default these messages
460 .\"only go to stderr and are not recorded anywhere else. Specifying a logfile
461 .\"copies messages to both stderr and the logfile.
463 .B loglevel <integer>
464 Specify the level at which debugging statements and operation
465 statistics should be syslogged (currently logged to the
467 LOG_LOCAL4 facility). Log levels are additive, and available levels
477 debug packet handling
480 heavy trace debugging
483 connection management
486 print out packets sent and received
489 search filter processing
492 configuration file processing
495 access control list processing
498 stats log connections/operations/results
501 stats log entries sent
504 print communication with shell backends
512 .B moduleload <filename>
513 Specify the name of a dynamically loadable module to load. The filename
514 may be an absolute path name or a simple filename. Non-absolute names
515 are searched for in the directories specified by the
517 option. This option and the
519 option are only usable if slapd was compiled with --enable-modules.
521 .B modulepath <pathspec>
522 Specify a list of directories to search for loadable modules. Typically
523 the path is colon-separated but this depends on the operating system.
526 .B objectclass "(\ <oid>\
528 [DESC\ <description]\
531 [{ ABSTRACT | STRUCTURAL | AUXILIARY }]\
532 [MUST\ <oids>] [MAY\ <oids>] )"
534 Specify an objectclass using the LDAPv3 syntax defined in RFC 2252.
535 The slapd parser extends the RFC 2252 definition by allowing string
536 forms as well as numeric OIDs to be used for the object class OID.
540 description.) Object classes are "STRUCTURAL" by default.
543 .B objectidentifier <name> "{ <oid> | <name>[:<suffix>] }"
544 Define a string name that equates to the given OID. The string can be used
545 in place of the numeric OID in objectclass and attribute definitions. The
546 name can also be used with a suffix of the form ":xx" in which case the
547 value "oid.xx" will be used.
549 .B password-hash <hash> [<hash>...]
550 This option configures one or more hashes to be used in generation of user
551 passwords stored in the userPassword attribute during processing of
552 LDAP Password Modify Extended Operations (RFC 3062).
553 The <hash> must be one of
567 use the SHA-1 algorithm (FIPS 160-1), the latter with a seed.
572 use the MD5 algorithm (RFC 1321), the latter with a seed.
579 indicates that the new password should be
580 added to userPassword as clear text.
582 Note that this option does not alter the normal user applications
583 handling of userPassword during LDAP Add, Modify, or other LDAP operations.
585 .B password\-crypt\-salt\-format <format>
586 Specify the format of the salt passed to
588 when generating {CRYPT} passwords (see
590 during processing of LDAP Password Modify Extended Operations (RFC 3062).
592 This string needs to be in
594 format and may include one (and only one) %s conversion.
595 This conversion will be substituted with a string random
596 characters from [A\-Za\-z0\-9./]. For example, "%.2s"
597 provides a two character salt and "$1$%.8s" tells some
598 versions of crypt(3) to use an MD5 algorithm and provides
599 8 random characters of salt. The default is "%s", which
600 provides 31 characters of salt.
602 .B pidfile <filename>
603 The ( absolute ) name of a file that will hold the
605 server's process ID ( see
607 ) if started without the debugging command line option.
610 Specify the referral to pass back when
612 cannot find a local database to handle a request.
613 If specified multiple times, each url is provided.
616 The ( absolute ) name of a file that will hold the
618 server's command line options
619 if started without the debugging command line option.
622 The ( absolute ) name of a file that will hold the
624 server's process ID ( see
626 ) if started without the debugging command line option.
628 .B require <conditions>
629 Specify a set of conditions (separated by white space) to
630 require (default none).
631 The directive may be specified globally and/or per-database.
633 requires bind operation prior to directory operations.
635 requires session to be using LDAP version 3.
637 requires authentication prior to directory operations.
639 requires SASL authentication prior to directory operations.
641 requires strong authentication prior to directory operations.
642 The strong keyword allows protected "simple" authentication
643 as well as SASL authentication.
645 may be used to require no conditions (useful for clearly globally
646 set conditions within a particular database).
648 .B reverse-lookup on | off
649 Enable/disable client name unverified reverse lookup (default is
651 if compiled with --enable-rlookups).
654 Specify the name of an LDIF(5) file containing user defined attributes
655 for the root DSE. These attributes are returned in addition to the
656 attributes normally produced by slapd.
658 .B sasl-authz-policy <policy>
659 Used to specify which rules to use for SASL Proxy Authorization. Proxy
660 authorization allows a client to authenticate to the server using one
661 user's credentials, but specify a different identity to use for authorization
662 and access control purposes. It essentially allows user A to login as user
663 B, using user A's password.
666 flag disables proxy authorization. This is the default setting.
669 flag will use rules in the
671 attribute of the authorization DN.
674 flag will use rules in the
676 attribute of the authentication DN.
679 flag, an alias for the deprecated value of
681 will allow any of the above, whatever succeeds first (checked in
687 flag requires both authorizations to succeed.
688 The rules are simply regular expressions specifying which DNs are allowed
689 to perform proxy authorization.
692 attribute in an entry specifies which other users
693 are allowed to proxy login to this entry. The
696 an entry specifies which other users this user can authorize as. Use of
699 abused if users are allowed to write arbitrary values to this attribute.
702 attribute must be protected with ACLs such that
703 only privileged users can modify it.
710 or a set of identities; it can take three forms:
714 .B ldap:///<base>??[<scope>]?<filter>
717 .B dn[.<dnstyle>]:<pattern>
720 .B u[<mech>[<realm>]]:<pattern>
727 .B <dnstyle>:={exact|onelevel|children|subtree|regex}
730 The first form is a valid LDAP
738 portions must be absent, so that the search occurs locally on either
744 with the optional style modifiers
750 for exact, onelevel, children and subtree matches, which cause
752 to be normalized according to the DN normalization rules, or the special
756 to be compiled according to
758 The third form is a SASL
760 with the optional fields
764 that allow to specify a SASL
766 and eventually a SASL
768 for those mechanisms that support one.
769 The need to allow the specification of a mechanism is still debated,
770 and users are strongly discouraged to rely on this possibility.
771 For backwards compatibility, if no identity type is provided, i.e. only
775 is assumed; as a consequence,
777 is subjected to DN normalization.
778 Since the interpretation of
782 can impact security, users are strongly encouraged
783 to explicitly set the type of identity specification that is being used.
787 Used to specify the fully qualified domain name used for SASL processing.
789 .B sasl-realm <realm>
790 Specify SASL realm. Default is empty.
792 .B sasl-regexp <match> <replace>
793 Used by the SASL mechanism to convert a SASL authenticated
794 username to an LDAP DN used for authorization purposes. Note that
795 the resultant DN need not refer to an existing entry to be considered
796 valid. When an authorization request is received, the SASL
800 are taken, when available, and combined into a SASL name of the
805 .B UID=<username>[[,CN=<realm>],CN=<mechanism>,]CN=auth
808 This SASL name is then compared against the
810 regular expression, and if the match is successful, the SASL name is
813 string. If there are wildcard strings in the
815 regular expression that are enclosed in parenthesis, e.g.
821 then the portion of the SASL name that matched the wildcard will be stored
822 in the numbered placeholder variable $1. If there are other wildcard strings
823 in parenthesis, the matching strings will be in $2, $3, etc. up to $9. The
824 placeholders can then be used in the
829 .B UID=$1,OU=Accounts,DC=example,DC=com
832 The replaced SASL name can be either a DN or an LDAP URI. If the
833 latter, the server will use the URI to search its own database(s)
834 and, if the search returns exactly one entry, the SASL name is
835 replaced by the DN of that entry. The LDAP URI must have no
836 hostport, attrs, or extensions components, e.g.
839 .B ldap:///OU=Accounts,DC=example,DC=com??one?(UID=$1)
844 options can be given in the configuration file to allow for multiple matching
845 and replacement patterns. The matching patterns are checked in the order they
846 appear in the file, stopping at the first successful match.
849 .\"Because the plus sign + is a character recognized by the regular expression engine,
850 .\"and it will appear in SASL names that include a REALM, be careful to escape the
851 .\"plus sign with a backslash \\+ to remove the character's special meaning.
854 .B sasl-secprops <properties>
855 Used to specify Cyrus SASL security properties.
858 flag (without any other properties) causes the flag properties
859 default, "noanonymous,noplain", to be cleared.
862 flag disables mechanisms susceptible to simple passive attacks.
865 flag disables mechanisms susceptible to active attacks.
868 flag disables mechanisms susceptible to passive dictionary attacks.
871 flag disables mechanisms which support anonymous login.
874 flag require forward secrecy between sessions.
877 require mechanisms which pass client credentials (and allow
878 mechanisms which can pass credentials to do so).
881 property specifies the minimum acceptable
882 .I security strength factor
883 as an integer approximate to effective key length used for
884 encryption. 0 (zero) implies no protection, 1 implies integrity
885 protection only, 56 allows DES or other weak ciphers, 112
886 allows triple DES and other strong ciphers, 128 allows RC4,
887 Blowfish and other modern strong ciphers. The default is 0.
890 property specifies the maximum acceptable
891 .I security strength factor
892 as an integer (see minssf description). The default is INT_MAX.
895 property specifies the maximum security layer receive buffer
896 size allowed. 0 disables security layers. The default is 65536.
899 Specify the distinguished name for the subschema subentry that
900 controls the entries on this server. The default is "cn=Subschema".
902 .B security <factors>
903 Specify a set of factors (separated by white space) to require.
904 An integer value is associated with each factor and is roughly
905 equivalent of the encryption key length to require. A value
906 of 112 is equivalent to 3DES, 128 to Blowfish, etc..
907 The directive may be specified globally and/or per-database.
909 specifies the overall security strength factor.
911 specifies the transport security strength factor.
913 specifies the TLS security strength factor.
915 specifies the SASL security strength factor.
917 specifies the overall security strength factor to require for
919 .B update_transport=<n>
920 specifies the transport security strength factor to require for
923 specifies the TLS security strength factor to require for
926 specifies the SASL security strength factor to require for
929 specifies the security strength factor required for
931 username/password authentication.
934 factor is measure of security provided by the underlying transport,
935 e.g. ldapi:// (and eventually IPSEC). It is not normally used.
937 .B sizelimit {<integer>|unlimited}
939 .B sizelimit size[.{soft|hard|unchecked}]=<integer> [...]
940 Specify the maximum number of entries to return from a search operation.
941 The default size limit is 500.
946 to specify no limits.
947 The second format allows a fine grain setting of the size limits.
948 Extra args can be added on the same line.
951 for an explanation of the different flags.
953 .B sockbuf_max_incoming <integer>
954 Specify the maximum incoming LDAP PDU size for anonymous sessions.
955 The default is 262143.
957 .B sockbuf_max_incoming_auth <integer>
958 Specify the maximum incoming LDAP PDU size for authenticated sessions.
959 The default is 4194303.
962 Specify the srvtab file in which the kerberos keys necessary for
963 authenticating clients using kerberos can be found. This option is only
964 meaningful if you are using Kerberos authentication.
967 Specify the maximum size of the primary thread pool.
970 .B timelimit {<integer>|unlimited}
972 .B timelimit time[.{soft|hard}]=<integer> [...]
973 Specify the maximum number of seconds (in real time)
975 will spend answering a search request. The default time limit is 3600.
980 to specify no limits.
981 The second format allows a fine grain setting of the time limits.
982 Extra args can be added on the same line.
985 for an explanation of the different flags.
987 .B ucdata-path <path>
988 Specify the path to the directory containing the Unicode character
989 tables. The default path is DATADIR/ucdata.
993 is built with support for Transport Layer Security, there are more options
996 .B TLSCipherSuite <cipher-suite-spec>
997 Permits configuring what ciphers will be accepted and the preference order.
998 <cipher-suite-spec> should be a cipher specification for OpenSSL. Example:
1000 TLSCipherSuite HIGH:MEDIUM:+SSLv2
1002 To check what ciphers a given spec selects, use:
1004 openssl ciphers -v <cipher-suite-spec>
1006 .B TLSCACertificateFile <filename>
1007 Specifies the file that contains certificates for all of the Certificate
1012 .B TLSCACertificatePath <path>
1013 Specifies the path of a directory that contains Certificate Authority
1014 certificates in separate individual files. Usually only one of this
1015 or the TLSCACertificateFile is used.
1017 .B TLSCertificateFile <filename>
1018 Specifies the file that contains the
1022 .B TLSCertificateKeyFile <filename>
1023 Specifies the file that contains the
1025 server private key that matches the certificate stored in the
1026 .B TLSCertificateFile
1027 file. Currently, the private key must not be protected with a password, so
1028 it is of critical importance that it is protected carefully.
1030 .B TLSRandFile <filename>
1031 Specifies the file to obtain random bits from when /dev/[u]random
1032 is not available. Generally set to the name of the EGD/PRNGD socket.
1033 The environment variable RANDFILE can also be used to specify the filename.
1035 .B TLSVerifyClient <level>
1036 Specifies what checks to perform on client certificates in an
1037 incoming TLS session, if any.
1040 can be specified as one of the following keywords:
1044 This is the default.
1046 will not ask the client for a certificate.
1049 The client certificate is requested. If no certificate is provided,
1050 the session proceeds normally. If a bad certificate is provided,
1051 it will be ignored and the session proceeds normally.
1054 The client certificate is requested. If no certificate is provided,
1055 the session proceeds normally. If a bad certificate is provided,
1056 the session is immediately terminated.
1058 .B demand | hard | true
1059 These keywords are all equivalent, for compatibility reasons.
1060 The client certificate is requested. If no certificate is provided,
1061 or a bad certificate is provided, the session is immediately terminated.
1063 Note that a valid client certificate is required in order to use the
1064 SASL EXTERNAL authentication mechanism with a TLS session. As such,
1067 setting must be chosen to enable SASL EXTERNAL authentication.
1069 .SH GENERAL BACKEND OPTIONS
1070 Options in this section only apply to the configuration file section
1071 for the specified backend. They are supported by every
1074 .B backend <databasetype>
1075 Mark the beginning of a backend definition. <databasetype>
1090 depending on which backend will serve the database.
1092 .SH GENERAL DATABASE OPTIONS
1093 Options in this section only apply to the configuration file section
1094 for the database in which they are defined. They are supported by every
1095 type of backend. Note that the
1099 option are mandatory for each database.
1101 .B database <databasetype>
1102 Mark the beginning of a new database instance definition. <databasetype>
1117 depending on which backend will serve the database.
1122 will automatically maintain the
1123 modifiersName, modifyTimestamp, creatorsName, and
1124 createTimestamp attributes for entries. By default, lastmod is on.
1126 .B maxderefdepth <depth>
1127 Specifies the maximum number of aliases to dereference when trying to
1128 resolve an entry, used to avoid infinite alias loops. The default is 1.
1130 .B overlay <overlay-name>
1131 Add the specified overlay to this database. An overlay is a piece of
1132 code that intercepts database operations in order to extend or change
1133 them. Overlays are pushed onto
1134 a stack over the database, and so they will execute in the reverse
1135 of the order in which they were configured and the database itself
1136 will receive control last of all.
1138 .B readonly on | off
1139 This option puts the database into "read-only" mode. Any attempts to
1140 modify the database will return an "unwilling to perform" error. By
1141 default, readonly is off.
1144 .B replica uri=ldap[s]://<hostname>[:port]|host=<hostname>[:port]
1145 .B [starttls=yes|critical]
1146 .B [suffix=<suffix> [...]]
1147 .B bindmethod=simple|sasl [binddn=<simple DN>] [credentials=<simple password>]
1148 .B [saslmech=<SASL mech>] [secprops=<properties>] [realm=<realm>]
1149 .B [authcId=<authentication ID>] [authzId=<authorization ID>]
1150 .B [attr[!]=<attr list>]
1152 Specify a replication site for this database. Refer to the "OpenLDAP
1153 Administrator's Guide" for detailed information on setting up a replicated
1155 directory service. Zero or more
1157 instances can be used to select the subtrees that will be replicated
1158 (defaults to all the database).
1160 is deprecated in favor of the
1164 allows the replica LDAP server to be specified as an LDAP URI.
1169 requires the options
1173 and should only be used when adequate security services
1174 (e.g TLS or IPSEC) are in place. A
1180 Specific security properties (as with the
1182 keyword above) for a SASL bind can be set with the
1184 option. A non-default SASL realm can be set with the
1189 will use Kerberos, a kerberos instance should be given in
1193 can be given after the
1195 keyword to allow the selective replication of the listed attributes only;
1198 mark is used, the list is considered exclusive, i.e. the listed attributes
1200 If an objectClass is listed, all the related attributes
1201 are (are not) replicated.
1204 .B replogfile <filename>
1205 Specify the name of the replication log file to log changes to.
1206 The replication log is typically written by
1211 .BR slapd.replog (5)
1212 for more information. The specified file should be located
1213 in a directory with limited read/write/execute access as the replication
1214 logs may contain sensitive information.
1217 Specify the distinguished name that is not subject to access control
1218 or administrative limit restrictions for operations on this database.
1219 This DN may or may not be associated with an entry. An empty root
1220 DN (the default) specifies no root access is to be granted. It is
1221 recommended that the rootdn only be specified when needed (such as
1222 when initially populating a database). If the rootdn is within
1223 a namingContext (suffix) of the database, a simple bind password
1224 may also be provided using the
1228 .B rootpw <password>
1229 Specify a password (or hash of the password) for the rootdn. The
1230 password can only be set if the rootdn is within the namingContext
1231 (suffix) of the database.
1232 This option accepts all RFC 2307 userPassword formats known to
1235 description) as well as cleartext.
1237 may be used to generate a hash of a password. Cleartext
1238 and \fB{CRYPT}\fP passwords are not recommended. If empty
1239 (the default), authentication of the root DN is by other means
1240 (e.g. SASL). Use of SASL is encouraged.
1242 .B suffix <dn suffix>
1243 Specify the DN suffix of queries that will be passed to this
1244 backend database. Multiple suffix lines can be given and at least one is
1245 required for each database definition.
1246 If the suffix of one database is "inside" that of another, the database
1247 with the inner suffix must come first in the configuration file.
1250 Specify that the current backend database is a subordinate of another
1251 backend database. A subordinate database may have only one suffix. This
1252 option may be used to glue multiple databases into a single namingContext.
1253 If the suffix of the current database is within the namingContext of a
1254 superior database, searches against the superior database will be
1255 propagated to the subordinate as well. All of the databases
1256 associated with a single namingContext should have identical rootdns.
1257 Behavior of other LDAP operations is unaffected by this setting. In
1258 particular, it is not possible to use moddn to move an entry from
1259 one subordinate to another subordinate within the namingContext.
1262 .B syncrepl rid=<replica ID>
1263 .B provider=ldap[s]://<hostname>[:port]
1264 .B [type=refreshOnly|refreshAndPersist]
1265 .B [interval=dd:hh:mm:ss]
1266 .B [searchbase=<base DN>]
1267 .B [filter=<filter str>]
1268 .B [scope=sub|one|base]
1269 .B [attrs=<attr list>]
1271 .B [sizelimit=<limit>]
1272 .B [timelimit=<limit>]
1273 .B [schemachecking=on|off]
1275 .B [bindmethod=simple|sasl]
1277 .B [saslmech=<mech>]
1278 .B [authcid=<identity>]
1279 .B [authzid=<identity>]
1280 .B [credentials=<passwd>]
1282 .B [secprops=<properties>]
1284 Specify the current database as a replica which is kept up-to-date with the
1285 master content by establishing the current
1287 as a replication consumer site running a
1290 The replica content is kept synchronized to the master content using
1291 the LDAP Content Synchronization protocol. Refer to the
1292 "OpenLDAP Administrator's Guide" for detailed information on
1293 setting up a replicated
1295 directory service using the
1299 identifies the current
1301 directive within the replication consumer site.
1302 It is a non-negative integer having no more than three digits.
1304 specifies the replication provider site containing the master content
1305 as an LDAP URI. If <port> is not given, the standard LDAP port number
1306 (389 or 636) is used. The content of the
1308 replica is defined using a search
1309 specification as its result set. The consumer
1311 will send search requests to the provider
1313 according to the search specification. The search specification includes
1314 .B searchbase, scope, filter, attrs, attrsonly, sizelimit,
1317 parameters as in the normal search specification.
1318 The search specification for the LDAP Content Synchronization operation
1319 has the same value syntax and the same default values as in the
1322 The LDAP Content Synchronization protocol has two operation types.
1325 operation, the next synchronization search operation
1326 is periodically rescheduled at an interval time (specified by
1328 parameter; 1 day by default)
1329 after each synchronization operation finishes.
1331 .B refreshAndPersist
1332 operation, a synchronization search remains persistent in the provider slapd.
1333 Further updates to the master replica will generate
1334 .B searchResultEntry
1335 to the consumer slapd as the search responses to the persistent
1336 synchronization search. The schema checking can be enforced at the LDAP Sync
1337 consumer site by turning on the
1339 parameter. The default is off.
1342 parameter specifies the DN in the consumer site
1343 which is allowed to make changes to the replica.
1344 The DN should have read/write access to the replica database.
1349 of the master database.
1354 requires the options
1358 and should only be used when adequate security services
1359 (e.g. TLS or IPSEC) are in place.
1366 Depending on the mechanism, an authentication identity and/or
1367 credentials can be specified using
1373 parameter may be used to specify an authorization identity.
1374 Specific security properties (as with the
1376 keyword above) for a SASL bind can be set with the
1378 option. A non default SASL realm can be set with the
1384 This option is only applicable in a slave
1386 It specifies the DN permitted to update (subject to access controls)
1387 the replica (typically, this is the DN
1389 binds to update the replica). Generally, this DN
1395 Specify the referral to pass back when
1397 is asked to modify a replicated local database.
1398 If specified multiple times, each url is provided.
1400 .SH DATABASE-SPECIFIC OPTIONS
1401 Each database may allow specific configuration options; they are
1402 documented separately in the backends' manual pages.
1404 The following backends can be compiled into slapd.
1405 They are documented in the
1406 .BR slapd-<backend> (5)
1410 This is the recommended backend for a normal slapd database.
1411 However, it takes more care than with the LDBM backend to configure
1413 It uses the Sleepycat Berkeley DB (BDB) package to store data.
1416 This is the database backend which is easiest to configure.
1417 However, it does not offer the data durability features of the BDB
1419 It uses Berkeley DB or GDBM to store data.
1422 This backend is experimental.
1423 It serves up referrals based upon SRV resource records held in the
1427 This backend acts as a proxy to forward incoming requests to another
1431 This backend performs basic LDAP proxying with respect to a set of
1432 remote LDAP servers. It is an enhancement of the ldap backend. The
1433 proxy cache extension of meta backend provides answering of search
1434 requests from the proxy using results of previously cached requests.
1437 This backend provides information about the running status of the slapd
1441 Operations in this backend succeed but do nothing.
1444 This backend is provided for demonstration purposes only.
1445 It serves up user account information from the system
1450 This backend embeds a
1452 interpreter into slapd.
1453 It runs Perl subroutines to implement LDAP operations.
1456 This backend executes external programs to implement LDAP operations.
1457 It is is primarily intended to be used in prototypes.
1460 This backend is experimental.
1461 It services LDAP requests from an SQL database.
1464 This backend is experimental.
1467 interpreter into slapd.
1468 It runs Tcl commands to implement LDAP operations.
1471 Here is a short example of a configuration file:
1475 include SYSCONFDIR/schema/core.schema
1476 pidfile LOCALSTATEDIR/slapd.pid
1478 # Subtypes of "name" (e.g. "cn" and "ou") with the
1479 # option ";x-hidden" can be searched for/compared,
1480 # but are not shown. See \fBslapd.access\fP(5).
1481 attributeoptions x-hidden lang-
1482 access to attr=name;x-hidden by * =cs
1485 suffix "dc=our-domain,dc=com"
1486 # The database directory MUST exist prior to
1487 # running slapd AND should only be accessible
1488 # by the slapd/tools. Mode 0700 recommended.
1489 directory LOCALSTATEDIR/openldap-data
1490 # Indices to maintain
1491 index objectClass eq
1492 index cn,sn,mail pres,eq,approx,sub
1494 # We serve small clients that do not handle referrals,
1495 # so handle remote lookups on their behalf.
1498 uri ldap://ldap.some-server.com/
1503 "OpenLDAP Administrator's Guide" contains a longer annotated
1504 example of a configuration file.
1505 The original ETCDIR/slapd.conf is another example.
1509 default slapd configuration file
1513 .BR slapd-dnssrv (5),
1517 .BR slapd-monitor (5),
1519 .BR slapd-passwd (5),
1521 .BR slapd-shell (5),
1524 .BR slapd.access (5),
1525 .BR slapd.plugin (5),
1526 .BR slapd.replog (5),
1534 "OpenLDAP Administrator's Guide" (http://www.OpenLDAP.org/doc/admin/)
1535 .SH ACKNOWLEDGEMENTS
1537 is developed and maintained by The OpenLDAP Project (http://www.openldap.org/).
1539 is derived from University of Michigan LDAP 3.3 Release.
projects / openldap / blob