2 # Copyright 1999-2003, The OpenLDAP Foundation, All Rights Reserved.
3 # COPYING RESTRICTIONS APPLY, see COPYRIGHT.
5 H1: The slapd Configuration File
7 Once the software has been built and installed, you are ready
8 to configure {{slapd}}(8) for use at your site. The slapd
9 runtime configuration is primarily accomplished through the
10 {{slapd.conf}}(5) file, normally installed in the
11 {{EX:/usr/local/etc/openldap}} directory.
13 An alternate configuration file can be specified via a
14 command-line option to {{slapd}}(8) or {{slurpd}}(8). This chapter
15 describes the general format of the config file, followed by a
16 detailed description of commonly used config file directives.
19 H2: Configuration File Format
21 The {{slapd.conf}}(5) file consists of three types of configuration
22 information: global, backend specific, and database specific. Global
23 information is specified first, followed by information associated
24 with a particular backend type, which is then followed by information
25 associated with a particular database instance. Global directives can
26 be overridden in backend and/or database directives, and backend directives
27 can be overridden by database directives.
29 Blank lines and comment lines beginning with a '{{EX:#}}' character
30 are ignored. If a line begins with white space, it is considered a
31 continuation of the previous line (even if the previous line is a
34 The general format of slapd.conf is as follows:
36 > # global configuration directives
37 > <global config directives>
39 > # backend definition
41 > <backend-specific directives>
43 > # first database definition & config directives
45 > <database-specific directives>
47 > # second database definition & config directives
49 > <database-specific directives>
51 > # second database definition & config directives
53 > <database-specific directives>
55 > # subsequent backend & database definitions & config directives
58 A configuration directive may take arguments. If so, they are
59 separated by white space. If an argument contains white space,
60 the argument should be enclosed in double quotes {{EX:"like this"}}. If
61 an argument contains a double quote or a backslash character `{{EX:\}}',
62 the character should be preceded by a backslash character `{{EX:\}}'.
64 The distribution contains an example configuration file that will
65 be installed in the {{F: /usr/local/etc/openldap}} directory.
66 A number of files containing schema definitions (attribute types
67 and object classes) are also provided in the
68 {{F: /usr/local/etc/openldap/schema}} directory.
71 H2: Configuration File Directives
73 This section details commonly used configuration directives. For
74 a complete list, see the {{slapd.conf}}(5) manual page. This section
75 separates the configuration file directives into global,
76 backend-specific and data-specific categories, describing each
77 directive and its default value (if any), and giving an example of
84 Directives described in this section apply to all backends
85 and databases unless specifically overridden in a backend or
86 database definition. Arguments that should be replaced
87 by actual text are shown in brackets {{EX:<>}}.
90 H4: access to <what> [ by <who> <accesslevel> <control> ]+
92 This directive grants access (specified by <accesslevel>) to a
93 set of entries and/or attributes (specified by <what>) by one or
94 more requesters (specified by <who>).
95 See the {{SECT:Access Control}} section of this chapter for a
96 summary of basic usage.
99 More details discussion of this directive can be found in the
100 {{SECT:Advanced Access Control}} chapter.
103 Note: If no {{EX:access}} directives are specified, the default
104 access control policy, {{EX:access to * by * read}}, allows all
105 both authenticated and anonymous users read access.
108 H4: attributetype <{{REF:RFC2252}} Attribute Type Description>
110 This directive defines an attribute type.
111 Please see the {{SECT:Schema Specification}} chapter
112 for information regarding how to use this directive.
114 H4: idletimeout <integer>
116 Specify the number of seconds to wait before forcibly closing
117 an idle client connection. An idletimeout of 0, the default,
118 disables this feature.
121 H4: include <filename>
123 This directive specifies that slapd should read additional
124 configuration information from the given file before continuing
125 with the next line of the current file. The included file should
126 follow the normal slapd config file format. The file is commonly
127 used to include files containing schema specifications.
129 Note: You should be careful when using this directive - there is
130 no small limit on the number of nested include directives, and no
131 loop detection is done.
133 H4: loglevel <integer>
135 This directive specifies the level at which debugging statements
136 and operation statistics should be syslogged (currently logged to
137 the {{syslogd}}(8) {{EX:LOG_LOCAL4}} facility). You must have
138 configured OpenLDAP {{EX:--enable-debug}} (the default) for this
139 to work (except for the two statistics levels, which are always
140 enabled). Log levels are additive. To display what numbers
141 correspond to what kind of debugging, invoke slapd with {{EX:-?}}
142 or consult the table below. The possible values for <integer> are:
144 !block table; colaligns="RL"; align=Center; \
145 title="Table 5.1: Debugging Levels"
147 -1 enable all debugging
149 1 trace function calls
150 2 debug packet handling
151 4 heavy trace debugging
152 8 connection management
153 16 print out packets sent and received
154 32 search filter processing
155 64 configuration file processing
156 128 access control list processing
157 256 stats log connections/operations/results
158 512 stats log entries sent
159 1024 print communication with shell backends
160 2048 print entry parsing debugging
167 This will cause lots and lots of debugging information to be
175 H4: objectclass <{{REF:RFC2252}} Object Class Description>
177 This directive defines an object class.
178 Please see the {{SECT:Schema Specification}} chapter for
179 information regarding how to use this directive.
184 This directive specifies the referral to pass back when slapd
185 cannot find a local database to handle a request.
189 > referral ldap://root.openldap.org
191 This will refer non-local queries to the global root LDAP server
192 at the OpenLDAP Project. Smart LDAP clients can re-ask their
193 query at that server, but note that most of these clients are
194 only going to know how to handle simple LDAP URLs that
195 contain a host part and optionally a distinguished name part.
198 H4: sizelimit <integer>
200 This directive specifies the maximum number of entries to return
201 from a search operation.
208 H4: timelimit <integer>
210 This directive specifies the maximum number of seconds (in real
211 time) slapd will spend answering a search request. If a
212 request is not finished in this time, a result indicating an
213 exceeded timelimit will be returned.
220 H3: General Backend Directives
222 Directives in this section apply only to the backend in which
223 they are defined. They are supported by every type of backend.
224 Backend directives apply to all databases instances of the
225 same type and, depending on the directive, may be overridden
226 by database directives.
230 This directive marks the beginning of a backend declaration.
231 {{EX:<type>}} should be one of the
232 supported backend types listed in Table 5.2.
234 !block table; align=Center; coltags="EX,N"; \
235 title="Table 5.2: Database Backends"
237 bdb Berkeley DB transactional backend
238 dnssrv DNS SRV backend
239 ldap Lightweight Directory Access Protocol (Proxy) backend
240 ldbm Lightweight DBM backend
241 meta Meta Directory backend
242 monitor Monitor backend
243 passwd Provides read-only access to {{passwd}}(5)
244 perl Perl Programmable backend
245 shell Shell (extern program) backend
246 sql SQL Programmable backend
253 This marks the beginning of a new {{TERM:BDB}} backend
257 H3: General Database Directives
259 Directives in this section apply only to the database in which
260 they are defined. They are supported by every type of database.
264 This directive marks the beginning of a database instance
266 {{EX:<type>}} should be one of the
267 supported backend types listed in Table 5.2.
273 This marks the beginning of a new {{TERM:BDB}} database instance
277 H4: readonly { on | off }
279 This directive puts the database into "read-only" mode. Any
280 attempts to modify the database will return an "unwilling to
289 > replica uri=ldap[s]://<hostname>[:<port>] | host=<hostname>[:<port>]
290 > [bindmethod={simple|kerberos|sasl}]
293 > [authcid=<identity>]
294 > [authzid=<identity>]
295 > [credentials=<password>]
296 > [srvtab=<filename>]
298 This directive specifies a replication site for this database. The
299 {{EX:uri=}} parameter specifies a scheme, a host and optionally a port where
300 the slave slapd instance can be found. Either a domain name
301 or IP address may be used for <hostname>. If <port> is not
302 given, the standard LDAP port number (389 or 636) is used.
304 {{EX:host}} is deprecated in favor of the {{EX:uri}} parameter.
306 {{EX:uri}} allows the replica LDAP server to be specified as an LDAP
307 URI such as {{EX:ldap://slave.example.com:389}} or
308 {{EX:ldaps://slave.example.com:636}}.
310 The {{EX:binddn=}} parameter gives the DN to bind as for updates
311 to the slave slapd. It should be a DN which has read/write access
312 to the slave slapd's database. It must also match the {{EX:updatedn}}
313 directive in the slave slapd's config file. Generally, this DN
314 {{should not}} be the same as the {{EX:rootdn}} of the master
315 database. Since DNs are likely to contain embedded spaces, the
316 entire {{EX:"binddn=<DN>"}} string should be enclosed in double
319 The {{EX:bindmethod}} is {{EX:simple}} or {{EX:kerberos}} or {{EX:sasl}},
320 depending on whether simple password-based authentication or Kerberos
321 authentication or {{TERM:SASL}} authentication is to be used when connecting
324 Simple authentication should not be used unless adequate integrity
325 and privacy protections are in place (e.g. TLS or IPSEC). Simple
326 authentication requires specification of {{EX:binddn}} and
327 {{EX:credentials}} parameters.
329 Kerberos authentication is deprecated in favor of SASL authentication
330 mechanisms, in particular the {{EX:KERBEROS_V4}} and {{EX:GSSAPI}}
331 mechanisms. Kerberos authentication requires {{EX:binddn}} and
332 {{EX:srvtab}} parameters.
334 SASL authentication is generally recommended. SASL authentication
335 requires specification of a mechanism using the {{EX:saslmech}} parameter.
336 Depending on the mechanism, an authentication identity and/or
337 credentials can be specified using {{EX:authcid}} and {{EX:credentials}}
338 respectively. The {{EX:authzid}} parameter may be used to specify
339 an authorization identity.
341 See the chapter entitled {{SECT:Replication with slurpd}} for more
342 information on how to use this directive.
345 H4: replogfile <filename>
347 This directive specifies the name of the replication log file to
348 which slapd will log changes. The replication log is typically
349 written by slapd and read by slurpd. Normally, this directive is
350 only used if slurpd is being used to replicate the database.
351 However, you can also use it to generate a transaction log, if
352 slurpd is not running. In this case, you will need to periodically
353 truncate the file, since it will grow indefinitely otherwise.
355 See the chapter entitled {{SECT:Replication with slurpd}} for more
356 information on how to use this directive.
361 This directive specifies the DN that is not subject to
362 access control or administrative limit restrictions for
363 operations on this database. The DN need not refer to
364 an entry in this database or even in the directory. The
365 DN may refer to a SASL identity.
369 > rootdn "cn=Manager,dc=example,dc=com"
373 > rootdn "uid=root,cn=example.com,cn=digest-md5,cn=auth"
375 See the {{SECT:SASL Authentication}} section for information on
376 SASL authentication identities.
379 H4: rootpw <password>
381 This directive can be used to specifies a password for the DN for
382 the rootdn (when the rootdn is set to a DN within the database).
388 It is also permissible to provide hash of the password in RFC 2307
389 form. {{slappasswd}}(8) may be used to generate the password hash.
393 > rootpw {SSHA}ZKKuqbEKJfKSXhUbHG3fG8MDn9j1v4QN
395 The hash was generated using the command {{EX:slappasswd -s secret}}.
398 H4: suffix <dn suffix>
400 This directive specifies the DN suffix of queries that will be
401 passed to this backend database. Multiple suffix lines can be
402 given, and at least one is required for each database
407 > suffix "dc=example,dc=com"
409 Queries with a DN ending in "dc=example,dc=com"
410 will be passed to this backend.
412 Note: When the backend to pass a query to is selected, slapd
413 looks at the suffix line(s) in each database definition in the
414 order they appear in the file. Thus, if one database suffix is a
415 prefix of another, it must appear after it in the config file.
420 > syncrepl rid=<replica ID>
421 > provider=ldap[s]://<hostname>[:port]
422 > [type=refreshOnly|refreshAndPersist]
423 > [interval=dd:hh:mm:ss]
424 > [searchbase=<base DN>]
425 > [filter=<filter str>]
426 > [scope=sub|one|base]
427 > [attrs=<attr list>]
429 > [sizelimit=<limit>]
430 > [timelimit=<limit>]
431 > [schemachecking=on|off]
433 > [bindmethod=simple|sasl]
436 > [authcid=<identity>]
437 > [authzid=<identity>]
438 > [credentials=<passwd>]
440 > [secprops=<properties>]
443 This directive specifies the current database as a replica of the
444 master content by establishing the current {{slapd}}(8) as a
445 replication consumer site running a syncrepl replication engine.
446 The master database is located at the replication provider site
447 specified by the {{EX:provider}} parameter. The replica database is
448 kept up-to-date with the master content using the LDAP Content
449 Synchronization protocol. See {{EX:draft-zeilenga-ldup-sync-xx.txt}}
450 ({{a work in progress}}) for more information on the protocol.
452 The {{EX:rid}} parameter is used for identification of the current
453 {{EX:syncrepl}} directive within the replication consumer server,
454 where {{EX:<replica ID>}} uniquely identifies the syncrepl specification
455 described by the current {{EX:syncrepl}} directive. {{EX:<replica ID>}}
456 is non-negative and is no more than three decimal digits in length.
458 The {{EX:provider}} parameter specifies the replication provider site
459 containing the master content as an LDAP URI. The {{EX:provider}}
460 parameter specifies a scheme, a host and optionally a port where the
461 provider slapd instance can be found. Either a domain name or IP
462 address may be used for <hostname>. Examples are
463 {{EX:ldap://provider.example.com:389}} or {{EX:ldaps://192.168.1.1:636}}.
464 If <port> is not given, the standard LDAP port number (389 or 636) is used.
465 Note that the syncrepl uses a consumer-initiated protocol, and hence its
466 specification is located at the consumer site, whereas the {{EX:replica}}
467 specification is located at the provider site. {{EX:syncrepl}} and
468 {{EX:replica}} directives define two independent replication
469 mechanisms. They do not represent the replication peers of each other.
471 The content of the syncrepl replica is defined using a search
472 specification as its result set. The consumer slapd will
473 send search requests to the provider slapd according to the search
474 specification. The search specification includes {{EX:searchbase}},
475 {{EX:scope}}, {{EX:filter}}, {{EX:attrs}}, {{EX:attrsonly}},
476 {{EX:sizelimit}}, and {{EX:timelimit}} parameters as in the normal
477 search specification. The syncrepl search specification has
478 the same value syntax and the same default values as in the
479 {{ldapsearch}}(1) client search tool.
481 The LDAP Content Synchronization protocol has two operation
482 types: {{EX:refreshOnly}} and {{EX:refreshAndPersist}}.
483 The operation type is specified by the {{EX:type}} parameter.
484 In the {{EX:refreshOnly}} operation, the next synchronization search operation
485 is periodically rescheduled at an interval time after each
486 synchronization operation finishes. The interval is specified
487 by the {{EX:interval}} parameter. It is set to one day by default.
488 In the {{EX:refreshAndPersist}} operation, a synchronization search
489 remains persistent in the provider slapd. Further updates to the
490 master replica will generate {{EX:searchResultEntry}} to the consumer slapd
491 as the search responses to the persistent synchronization search.
493 The schema checking can be enforced at the LDAP Sync consumer site
494 by turning on the {{EX:schemachecking}} parameter.
495 If it is turned on, every replicated entry will be checked for its
496 schema as the entry is stored into the replica content.
497 Every entry in the replica should contain those attributes
498 required by the schema definition.
499 If it is turned off, entries will be stored without checking
500 schema conformance. The default is off.
502 The {{EX:updatedn}} parameter specifies the DN in the consumer site
503 which is allowed to make changes to the replica. This DN is used
504 locally by the syncrepl engine when updating the replica with the
505 entries received from the provider site by using the internal
506 operation mechanism. The update of the replica content is subject
507 to the access control privileges of the DN. The DN should have
508 read/write access to the replica database. Generally, this DN
509 {{should not}} be the same as {{EX:rootdn}}.
511 The {{EX:binddn}} parameter gives the DN to bind as for the
512 syncrepl searches to the provider slapd. It should be a DN
513 which has read access to the replication content in the
516 The {{EX:bindmethod}} is {{EX:simple}} or {{EX:sasl}},
517 depending on whether simple password-based authentication or
518 {{TERM:SASL}} authentication is to be used when connecting
519 to the provider slapd.
521 Simple authentication should not be used unless adequate integrity
522 and privacy protections are in place (e.g. TLS or IPSEC). Simple
523 authentication requires specification of {{EX:binddn}} and
524 {{EX:credentials}} parameters.
526 SASL authentication is generally recommended. SASL authentication
527 requires specification of a mechanism using the {{EX:saslmech}} parameter.
528 Depending on the mechanism, an authentication identity and/or
529 credentials can be specified using {{EX:authcid}} and {{EX:credentials}},
530 respectively. The {{EX:authzid}} parameter may be used to specify
531 an authorization identity.
533 The {{EX:realm}} parameter specifies a realm which a certain
534 mechanisms authenticate the identity within. The {{EX:secprops}}
535 parameter specifies Cyrus SASL security properties.
537 The syncrepl replication mechanism is supported by the
538 three native backends: back-bdb, back-hdb, and back-ldbm.
540 See the {{SECT:LDAP Sync Replication}} chapter of the admin guide
541 for more information on how to use this directive.
546 This directive is only applicable in a slave slapd. It specifies
547 the DN allowed to make changes to the replica. This may be the DN
548 {{slurpd}}(8) binds as when making changes to the replica or the DN
549 associated with a SASL identity.
553 > updatedn "cn=Update Daemon,dc=example,dc=com"
557 > updatedn "uid=slurpd,cn=example.com,cn=digest-md5,cn=auth"
559 See the {{SECT:Replication with slurpd}} chapter for more information
560 on how to use this directive.
564 This directive is only applicable in a slave slapd. It
565 specifies the URL to return to clients which submit update
566 requests upon the replica.
567 If specified multiple times, each {{TERM:URL}} is provided.
571 > updateref ldap://master.example.net
574 H3: BDB Database Directives
576 Directives in this category only apply to a {{TERM:BDB}} database.
577 That is, they must follow a "database bdb" line and come before any
578 subsequent "backend" or "database" line. For a complete reference
579 of BDB configuration directives, see {{slapd-bdb}}(5).
582 H4: directory <directory>
584 This directive specifies the directory where the BDB files
585 containing the database and associated indices live.
589 > directory /usr/local/var/openldap-data
592 H4: sessionlog <sid> <limit>
594 This directive specifies a session log store in the syncrepl
595 replication provider server which contains information on
596 the entries that have been scoped out of the replication
597 content identified by {{EX:<sid>}}.
598 The first syncrepl search request having the same {{EX:<sid>}} value
599 in the cookie establishes the session log store in the provider server.
600 The number of the entries in the session log store is limited
601 by {{EX:<limit>}}. Excessive entries are removed from the store
602 in the FIFO order. Both {{EX:<sid>}} and {{EX:<limit>}} are
603 non-negative integers. {{EX:<sid>}} has no more than three decimal digits.
605 The LDAP Content Synchronization operation that falls into a pre-existing
606 session can use the session log store in order to reduce the amount
607 of synchronization traffic. If the replica is not so outdated that
608 it can be made up-to-date by the information in the session store,
609 the provider slapd will send the consumer slapd the identities of the
610 scoped-out entries together with the in-scope entries added to or
611 modified within the replication content. If the replica status is
612 outdated too much and beyond the coverage of the history store,
613 then the provider slapd will send the identities of the unchanged
614 in-scope entries along with the changed in-scope entries.
615 The consumer slapd will then remove those entries in the replica
616 which are not identified as present in the provider content.
619 H3: LDBM Database Directives
621 Directives in this category only apply to a {{TERM:LDBM}} database.
622 That is, they must follow a "database ldbm" line and come before
623 any subsequent "backend" or "database" line. For a complete reference
624 of LDBM configuration directives, see {{slapd-ldbm}}(5).
626 H4: cachesize <integer>
628 This directive specifies the size in entries of the in-memory
629 cache maintained by the LDBM backend database instance.
636 H4: dbcachesize <integer>
638 This directive specifies the size in bytes of the in-memory cache
639 associated with each open index file. If not supported by the
640 underlying database method, this directive is ignored without
641 comment. Increasing this number uses more memory but can
642 cause a dramatic performance increase, especially during
643 modifies or when building indices.
652 This option, if present, disables database locking.
653 Enabling this option may improve performance at the expense
659 This option causes on-disk database contents to not be immediately
660 synchronized with in memory changes upon change. Enabling this option
661 may improve performance at the expense of data integrity.
664 H4: directory <directory>
666 This directive specifies the directory where the LDBM files
667 containing the database and associated indices live.
671 > directory /usr/local/var/openldap-data
674 H4: index {<attrlist> | default} [pres,eq,approx,sub,none]
676 This directive specifies the indices to maintain for the given
677 attribute. If only an {{EX:<attrlist>}} is given, the default
678 indices are maintained.
682 > index default pres,eq
684 > index cn,sn pres,eq,sub
685 > index objectClass eq
687 The first line sets the default set of indices to maintain to
688 present and equality. The second line causes the default (pres,eq)
689 set of indices to be maintained for the {{EX:uid}} attribute type.
690 The third line causes present, equality, and substring indices to
691 be maintained for {{EX:cn}} and {{EX:sn}} attribute types. The
692 fourth line causes an equality index for the {{EX:objectClass}}
695 By default, no indices are maintained. It is generally advised
696 that minimally an equality index upon objectClass be maintained.
698 > index objectClass eq
704 This directive specifies the file protection mode that newly
705 created database index files should have.
714 Access to slapd entries and attributes is controlled by the
715 access configuration file directive. The general form of an
718 > <access directive> ::= access to <what>
719 > [by <who> <access> <control>]+
721 > [dn[.<basic-style>]=<regex> | dn.<scope-style>=<DN>]
722 > [filter=<ldapfilter>] [attrs=<attrlist>]
723 > <basic-style> ::= regex | exact
724 > <scope-style> ::= base | one | subtree | children
725 > <attrlist> ::= <attr> [val[.<basic-style>]=<regex>] | <attr> , <attrlist>
726 > <attr> ::= <attrname> | entry | children
727 > <who> ::= * | [anonymous | users | self
728 > | dn[.<basic-style>]=<regex> | dn.<scope-style>=<DN>]
729 > [dnattr=<attrname>]
730 > [group[/<objectclass>[/<attrname>][.<basic-style>]]=<regex>]
731 > [peername[.<basic-style>]=<regex>]
732 > [sockname[.<basic-style>]=<regex>]
733 > [domain[.<basic-style>]=<regex>]
734 > [sockurl[.<basic-style>]=<regex>]
737 > <access> ::= [self]{<level>|<priv>}
738 > <level> ::= none | auth | compare | search | read | write
739 > <priv> ::= {=|+|-}{w|r|s|c|x|0}+
740 > <control> ::= [stop | continue | break]
742 where the <what> part selects the entries and/or attributes to which
743 the access applies, the {{EX:<who>}} part specifies which entities
744 are granted access, and the {{EX:<access>}} part specifies the
745 access granted. Multiple {{EX:<who> <access> <control>}} triplets
746 are supported, allowing many entities to be granted different access
747 to the same set of entries and attributes. Not all of these access
748 control options are described here; for more details see the
749 {{slapd.access}}(5) man page.
752 H3: What to control access to
754 The <what> part of an access specification determines the entries
755 and attributes to which the access control applies. Entries are
756 commonly selected in two ways: by DN and by filter. The following
757 qualifiers select entries by DN:
760 > to dn[.<basic-style>]=<regex>
761 > to dn.<scope-style>=<DN>
763 The first form is used to select all entries. The second form may
764 be used to select entries by matching a regular expression against
765 the target entry's {{normalized DN}}. (The second form is not
766 discussed further in this document.) The third form is used to
767 select entries which are within the requested scope of DN. The
768 <DN> is a string representation of the Distinguished Name, as
769 described in {{REF:RFC2253}}.
771 The scope can be either {{EX:base}}, {{EX:one}}, {{EX:subtree}},
772 or {{EX:children}}. Where {{EX:base}} matches only the entry with
773 provided DN, {{EX:one}} matches the entries whose parent is the
774 provided DN, {{EX:subtree}} matches all entries in the subtree whose
775 root is the provided DN, and {{EX:children}} matches all entries
776 under the DN (but not the entry named by the DN).
778 For example, if the directory contained entries named:
781 > 1: cn=Manager,o=suffix
782 > 2: ou=people,o=suffix
783 > 3: uid=kdz,ou=people,o=suffix
784 > 4: cn=addresses,uid=kdz,ou=people,o=suffix
785 > 5: uid=hyc,ou=people,o=suffix
788 . {{EX:dn.base="ou=people,o=suffix"}} match 2;
789 . {{EX:dn.one="ou=people,o=suffix"}} match 3, and 5;
790 . {{EX:dn.subtree="ou=people,o=suffix"}} match 2, 3, 4, and 5; and
791 . {{EX:dn.children="ou=people,o=suffix"}} match 3, 4, and 5.
794 Entries may also be selected using a filter:
796 > to filter=<ldap filter>
798 where <ldap filter> is a string representation of an LDAP
799 search filter, as described in {{REF:RFC2254}}. For example:
801 > to filter=(objectClass=person)
803 Note that entries may be selected by both DN and filter by
804 including both qualifiers in the <what> clause.
806 > to dn.one="ou=people,o=suffix" filter=(objectClass=person)
808 Attributes within an entry are selected by including a comma-separated
809 list of attribute names in the <what> selector:
811 > attrs=<attribute list>
813 A specific value of an attribute is selected by using a single
814 attribute name and also using a value selector:
816 > attrs=<attribute> val[.<style>]=<regex>
818 There are two special {{pseudo}} attributes {{EX:entry}} and
819 {{EX:children}}. To read (and hence return) a target entry, the
820 subject must have {{EX:read}} access to the target's {{entry}}
821 attribute. To add or delete an entry, the subject must have
822 {{EX:write}} access to the entry's {{EX:entry}} attribute AND must
823 have {{EX:write}} access to the entry's parent's {{EX:children}}
824 attribute. To rename an entry, the subject must have {{EX:write}}
825 access to entry's {{EX:entry}} attribute AND have {{EX:write}}
826 access to both the old parent's and new parent's {{EX:children}}
827 attributes. The complete examples at the end of this section should
828 help clear things up.
830 Lastly, there is a special entry selector {{EX:"*"}} that is used to
831 select any entry. It is used when no other {{EX:<what>}}
832 selector has been provided. It's equivalent to "{{EX:dn=.*}}"
835 H3: Who to grant access to
837 The <who> part identifies the entity or entities being granted
838 access. Note that access is granted to "entities" not "entries."
839 The following table summarizes entity specifiers:
841 !block table; align=Center; coltags="EX,N"; \
842 title="Table 5.3: Access Entity Specifiers"
844 *|All, including anonymous and authenticated users
845 anonymous|Anonymous (non-authenticated) users
846 users|Authenticated users
847 self|User associated with target entry
848 dn[.<basic-style>]=<regex>|Users matching a regular expression
849 dn.<scope-style>=<DN>|Users within scope of a DN
852 The DN specifier behaves much like <what> clause DN specifiers.
854 Other control factors are also supported. For example, a {{EX:<who>}}
855 can be restricted by an entry listed in a DN-valued attribute in
856 the entry to which the access applies:
858 > dnattr=<dn-valued attribute name>
860 The dnattr specification is used to give access to an entry
861 whose DN is listed in an attribute of the entry (e.g., give
862 access to a group entry to whoever is listed as the owner of
865 Some factors may not be appropriate in all environments (or any).
866 For example, the domain factor relies on IP to domain name lookups.
867 As these can easily spoofed, the domain factor should not be avoided.
870 H3: The access to grant
873 The kind of <access> granted can be one of the following:
876 !block table; colaligns="LRL"; coltags="EX,EX,N"; align=Center; \
877 title="Table 5.4: Access Levels"
878 Level Privileges Description
880 auth =x needed to bind
881 compare =cx needed to compare
882 search =scx needed to apply search filters
883 read =rscx needed to read search results
884 write =wrscx needed to modify/rename
887 Each level implies all lower levels of access. So, for
888 example, granting someone {{EX:write}} access to an entry also
889 grants them {{EX:read}}, {{EX:search}}, {{EX:compare}}, and
890 {{EX:auth}} access. However, one may use the privileges specifier
891 to grant specific permissions.
894 H3: Access Control Evaluation
896 When evaluating whether some requester should be given access to
897 an entry and/or attribute, slapd compares the entry and/or attribute
898 to the {{EX:<what>}} selectors given in the configuration file.
899 For each entry, access controls provided in the database which holds
900 the entry (or the first database if not held in any database) apply
901 first, followed by the global access directives. Within this
902 priority, access directives are examined in the order in which they
903 appear in the config file. Slapd stops with the first {{EX:<what>}}
904 selector that matches the entry and/or attribute. The corresponding
905 access directive is the one slapd will use to evaluate access.
907 Next, slapd compares the entity requesting access to the {{EX:<who>}}
908 selectors within the access directive selected above in the order
909 in which they appear. It stops with the first {{EX:<who>}} selector
910 that matches the requester. This determines the access the entity
911 requesting access has to the entry and/or attribute.
913 Finally, slapd compares the access granted in the selected
914 {{EX:<access>}} clause to the access requested by the client. If
915 it allows greater or equal access, access is granted. Otherwise,
918 The order of evaluation of access directives makes their placement
919 in the configuration file important. If one access directive is
920 more specific than another in terms of the entries it selects, it
921 should appear first in the config file. Similarly, if one {{EX:<who>}}
922 selector is more specific than another it should come first in the
923 access directive. The access control examples given below should
924 help make this clear.
928 H3: Access Control Examples
930 The access control facility described above is quite powerful. This
931 section shows some examples of its use for descriptive purposes.
935 > access to * by * read
937 This access directive grants read access to everyone.
944 This directive allows the user to modify their entry, allows anonymous
945 to authentication against these entries, and allows all others to
946 read these entries. Note that only the first {{EX:by <who>}} clause
947 which matches applies. Hence, the anonymous users are granted
948 {{EX:auth}}, not {{EX:read}}. The last clause could just as well
949 have been "{{EX:by users read}}".
951 It is often desirable to restrict operations based upon the level
952 of protection in place. The following shows how security strength
953 factors (SSF) can be used.
956 > by ssf=128 self write
957 > by ssf=64 anonymous auth
958 > by ssf=64 users read
960 This directive allows users to modify their own entries if security
961 protections have of strength 128 or better have been established,
962 allows authentication access to anonymous users, and read access
963 when 64 or better security protections have been established. If
964 client has not establish sufficient security protections, the
965 implicit {{EX:by * none}} clause would be applied.
967 The following example shows the use of a style specifiers to select
968 the entries by DN in two access directives where ordering is
971 > access to dn.children="dc=example,dc=com"
973 > access to dn.children="dc=com"
976 Read access is granted to entries under the {{EX:dc=com}} subtree,
977 except for those entries under the {{EX:dc=example,dc=com}} subtree,
978 to which search access is granted. No access is granted to
979 {{EX:dc=com}} as neither access directive matches this DN. If the
980 order of these access directives was reversed, the trailing directive
981 would never be reached, since all entries under {{EX:dc=example,dc=com}}
982 are also under {{EX:dc=com}} entries.
984 Also note that if no {{EX:access to}} directive matches or no {{EX:by
985 <who>}} clause, {{B:access is denied}}. That is, every {{EX:access
986 to}} directive ends with an implicit {{EX:by * none}} clause and
987 every access list ends with an implicit {{EX:access to * by * none}}
990 The next example again shows the importance of ordering, both of
991 the access directives and the {{EX:by <who>}} clauses. It also
992 shows the use of an attribute selector to grant access to a specific
993 attribute and various {{EX:<who>}} selectors.
995 > access to dn.subtree="dc=example,dc=com" attr=homePhone
997 > by dn.children=dc=example,dc=com" search
998 > by peername.regex=IP:10\..+ read
999 > access to dn.subtree="dc=example,dc=com"
1001 > by dn.children="dc=example,dc=com" search
1004 This example applies to entries in the "{{EX:dc=example,dc=com}}"
1005 subtree. To all attributes except {{EX:homePhone}}, an entry can
1006 write to itself, entries under {{EX:example.com}} entries can search
1007 by them, anybody else has no access (implicit {{EX:by * none}})
1008 excepting for authentication/authorization (which is always done
1009 anonymously). The {{EX:homePhone}} attribute is writable by the
1010 entry, searchable by entries under {{EX:example.com}}, readable by
1011 clients connecting from network 10, and otherwise not readable
1012 (implicit {{EX:by * none}}). All other access is denied by the
1013 implicit {{EX:access to * by * none}}.
1015 Sometimes it is useful to permit a particular DN to add or
1016 remove itself from an attribute. For example, if you would like to
1017 create a group and allow people to add and remove only
1018 their own DN from the member attribute, you could accomplish
1019 it with an access directive like this:
1021 > access to attr=member,entry
1022 > by dnattr=member selfwrite
1024 The dnattr {{EX:<who>}} selector says that the access applies to
1025 entries listed in the {{EX:member}} attribute. The {{EX:selfwrite}} access
1026 selector says that such members can only add or delete their
1027 own DN from the attribute, not other values. The addition of
1028 the entry attribute is required because access to the entry is
1029 required to access any of the entry's attributes.
1032 For more details on how to use the {{EX:access}} directive,
1033 consult the {{Advanced Access Control}} chapter.
1037 H2: Configuration File Example
1039 The following is an example configuration file, interspersed
1040 with explanatory text. It defines two databases to handle
1041 different parts of the {{TERM:X.500}} tree; both are {{TERM:BDB}}
1042 database instances. The line numbers shown are provided for
1043 reference only and are not included in the actual file. First, the
1044 global configuration section:
1046 E: 1. # example config file - global configuration section
1047 E: 2. include /usr/local/etc/schema/core.schema
1048 E: 3. referral ldap://root.openldap.org
1049 E: 4. access to * by * read
1051 Line 1 is a comment. Line 2 includes another config file
1052 which contains {{core}} schema definitions.
1053 The {{EX:referral}} directive on line 3
1054 means that queries not local to one of the databases defined
1055 below will be referred to the LDAP server running on the
1056 standard port (389) at the host {{EX:root.openldap.org}}.
1058 Line 4 is a global access control. It applies to all
1059 entries (after any applicable database-specific access
1062 The next section of the configuration file defines a BDB
1063 backend that will handle queries for things in the
1064 "dc=example,dc=com" portion of the tree. The
1065 database is to be replicated to two slave slapds, one on
1066 truelies, the other on judgmentday. Indices are to be
1067 maintained for several attributes, and the {{EX:userPassword}}
1068 attribute is to be protected from unauthorized access.
1070 E: 5. # BDB definition for the example.com
1072 E: 7. suffix "dc=example,dc=com"
1073 E: 8. directory /usr/local/var/openldap-data
1074 E: 9. rootdn "cn=Manager,dc=example,dc=com"
1075 E: 10. rootpw secret
1076 E: 11. # replication directives
1077 E: 12. replogfile /usr/local/var/openldap/slapd.replog
1078 E: 13. replica uri=ldap://slave1.example.com:389
1079 E: 14. binddn="cn=Replicator,dc=example,dc=com"
1080 E: 15. bindmethod=simple credentials=secret
1081 E: 16. replica uri=ldaps://slave2.example.com:636
1082 E: 17. binddn="cn=Replicator,dc=example,dc=com"
1083 E: 18. bindmethod=simple credentials=secret
1084 E: 19. # indexed attribute definitions
1085 E: 20. index uid pres,eq
1086 E: 21. index cn,sn,uid pres,eq,approx,sub
1087 E: 22. index objectClass eq
1088 E: 23. # database access control definitions
1089 E: 24. access to attr=userPassword
1090 E: 25. by self write
1091 E: 26. by anonymous auth
1092 E: 27. by dn.base="cn=Admin,dc=example,dc=com" write
1095 E: 30. by self write
1096 E: 31. by dn.base="cn=Admin,dc=example,dc=com" write
1099 Line 5 is a comment. The start of the database definition is marked
1100 by the database keyword on line 6. Line 7 specifies the DN suffix
1101 for queries to pass to this database. Line 8 specifies the directory
1102 in which the database files will live.
1104 Lines 9 and 10 identify the database {{super-user}} entry and associated
1105 password. This entry is not subject to access control or size or
1106 time limit restrictions.
1108 Lines 11 through 18 are for replication. Line 12 specifies the
1109 replication log file (where changes to the database are logged -
1110 this file is written by slapd and read by slurpd). Lines 13 through
1111 15 specify the hostname and port for a replicated host, the DN to
1112 bind as when performing updates, the bind method (simple) and the
1113 credentials (password) for the binddn. Lines 16 through 18 specify
1114 a second replication site. See the {{SECT:Replication with slurpd}}
1115 chapter for more information on these directives.
1117 Lines 20 through 22 indicate the indices to maintain for various
1120 Lines 24 through 32 specify access control for entries in this
1121 database. As this is the first database, the controls also apply
1122 to entries not held in any database (such as the Root DSE). For
1123 all applicable entries, the {{EX:userPassword}} attribute is writable
1124 by the entry itself and by the "admin" entry. It may be used for
1125 authentication/authorization purposes, but is otherwise not readable.
1126 All other attributes are writable by the entry and the "admin"
1127 entry, but may be read by all users (authenticated or not).
1129 The next section of the example configuration file defines another
1130 BDB database. This one handles queries involving the
1131 {{EX:dc=example,dc=net}} subtree but is managed by the same entity
1132 as the first database. Note that without line 39, the read access
1133 would be allowed due to the global access rule at line 4.
1135 E: 33. # BDB definition for example.net
1137 E: 35. suffix "dc=example,dc=net"
1138 E: 36. directory /usr/local/var/openldap-data-net
1139 E: 37. rootdn "cn=Manager,dc=example,dc=com"
1140 E: 38. index objectClass eq
1141 E: 39. access to * by users read