1 .TH SLAPD-LDAP 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2014 The OpenLDAP Foundation All Rights Reserved.
3 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
6 slapd\-ldap \- LDAP backend to slapd
12 is not an actual database; instead it acts as a proxy to forward incoming
13 requests to another LDAP server. While processing requests it will also
14 chase referrals, so that referrals are fully processed instead of being
15 returned to the slapd client.
17 Sessions that explicitly Bind to the back-ldap database always create their
18 own private connection to the remote LDAP server. Anonymous sessions will
19 share a single anonymous connection to the remote server. For sessions bound
20 through other mechanisms, all sessions with the same DN will share the
21 same connection. This connection pooling strategy can enhance the proxy's
22 efficiency by reducing the overhead of repeatedly making/breaking multiple
25 The ldap database can also act as an information service, i.e. the identity
26 of locally authenticated clients is asserted to the remote server, possibly
27 in some modified form.
28 For this purpose, the proxy binds to the remote server with some
29 administrative identity, and, if required, authorizes the asserted identity.
33 The administrative identity of the proxy, on the remote server, must be
34 allowed to authorize by means of appropriate
42 must contain schema information for the attributes and objectClasses
43 used in filters, request DNs and request-related data in general.
44 It should also contain schema information for the data returned
45 by the proxied server.
46 It is the responsibility of the proxy administrator to keep the schema
47 of the proxy lined up with that of the proxied server.
50 Note: When looping back to the same instance of
52 each connection requires a new thread; as a consequence,
54 must be compiled with thread support, and the \fBthreads\fP parameter
55 may need some tuning; in those cases, one may consider using
57 instead, which performs the relayed operation
58 internally and thus reuses the same connection.
63 options apply to the LDAP backend database.
64 That is, they must follow a "database ldap" line and come before any
65 subsequent "backend" or "database" lines.
66 Other database options are described in the
71 Note: In early versions of back-ldap it was recommended to always set
84 This was required because operational attributes related to entry creation
85 and modification should not be proxied, as they could be mistakenly written
86 to the target server(s), generating an error.
87 The current implementation automatically sets lastmod to \fBoff\fP,
88 so its use is redundant and should be omitted.
92 LDAP server to use. Multiple URIs can be set in a single
94 argument, resulting in the underlying library automatically
95 calling the first server of the list that responds, e.g.
97 \fBuri "ldap://host/ ldap://backup\-host/"\fP
99 The URI list is space- or comma-separated.
100 Whenever the server that responds is not the first one in the list,
101 the list is rearranged and the responsive server is moved to the head,
102 so that it will be first contacted the next time a connection
107 .B bindmethod=simple|sasl [binddn=<simple DN>] [credentials=<simple password>]
108 .B [saslmech=<SASL mech>] [secprops=<properties>] [realm=<realm>]
109 .B [authcId=<authentication ID>] [authzId=<authorization ID>]
110 .B [starttls=no|yes|critical]
113 .B [tls_cacert=<file>]
114 .B [tls_cacertdir=<path>]
115 .B [tls_reqcert=never|allow|try|demand]
116 .B [tls_ciphersuite=<ciphers>]
117 .B [tls_protocol_min=<major>[.<minor>]]
118 .B [tls_crlcheck=none|peer|all]
120 Allows to define the parameters of the authentication method that is
121 internally used by the proxy to collect info related to access control,
122 and whenever an operation occurs with the identity of the rootdn
123 of the LDAP proxy database.
124 The identity defined by this directive, according to the properties
125 associated to the authentication method, is supposed to have read access
126 on the target server to attributes used on the proxy for ACL checking.
128 There is no risk of giving away such values; they are only used to
130 The default is to use
132 bind, with empty \fIbinddn\fP and \fIcredentials\fP,
133 which means that the related operations will be performed anonymously.
134 If not set, and if \fBidassert\-bind\fP is defined, this latter identity
135 is used instead. See \fBidassert\-bind\fP for details.
137 The connection between the proxy database and the remote server
138 associated to this identity is cached regardless of the lifespan
139 of the client-proxy connection that first established it.
141 .B This identity is not implicitly used by the proxy
142 .B when the client connects anonymously.
145 feature, instead, in some cases can be crafted to implement that behavior,
146 which is \fIintrinsically unsafe and should be used with extreme care\fP.
147 This directive obsoletes
152 The TLS settings default to the same as the main slapd TLS settings,
155 which defaults to "demand".
159 .B cancel {ABANDON|ignore|exop[\-discover]}
160 Defines how to handle operation cancellation.
163 is invoked, so the operation is abandoned immediately.
166 no action is taken and any further response is ignored; this may result
167 in further response messages to be queued for that connection, so it is
168 recommended that long lasting connections are timed out either by
172 so that resources eventually get released.
177 operation (RFC 3909) is issued, resulting in the cancellation
178 of the current operation; the
180 operation waits for remote server response, so its use
181 may not be recommended.
186 extended operation is detected by reading the remote server's root DSE.
189 .B chase\-referrals {YES|no}
190 enable/disable automatic referral chasing, which is delegated to the
191 underlying libldap, with rebinding eventually performed if the
192 \fBrebind\-as\-user\fP directive is used. The default is to chase referrals.
196 This directive causes a cached connection to be dropped and recreated
197 after a given ttl, regardless of being idle or not.
200 .B idassert\-authzFrom <authz-regexp>
201 if defined, selects what
203 identities are authorized to exploit the identity assertion feature.
206 follows the rules defined for the
213 for details on the syntax of this field.
218 .B bindmethod=none|simple|sasl [binddn=<simple DN>] [credentials=<simple password>]
219 .B [saslmech=<SASL mech>] [secprops=<properties>] [realm=<realm>]
220 .B [authcId=<authentication ID>] [authzId=<authorization ID>]
221 .B [authz={native|proxyauthz}] [mode=<mode>] [flags=<flags>]
222 .B [starttls=no|yes|critical]
225 .B [tls_cacert=<file>]
226 .B [tls_cacertdir=<path>]
227 .B [tls_reqcert=never|allow|try|demand]
228 .B [tls_ciphersuite=<ciphers>]
229 .B [tls_protocol_min=<version>]
230 .B [tls_crlcheck=none|peer|all]
232 Allows to define the parameters of the authentication method that is
233 internally used by the proxy to authorize connections that are
234 authenticated by other databases.
235 Direct binds are always proxied without any idassert handling.
237 The identity defined by this directive, according to the properties
238 associated to the authentication method, is supposed to have auth access
239 on the target server to attributes used on the proxy for authentication
240 and authorization, and to be allowed to authorize the users.
241 This requires to have
243 privileges on a wide set of DNs, e.g.
244 .BR authzTo=dn.subtree:"" ,
245 and the remote server to have
253 for details on these statements and for remarks and drawbacks about
255 The supported bindmethods are
257 \fBnone|simple|sasl\fP
261 is the default, i.e. no \fIidentity assertion\fP is performed.
263 The authz parameter is used to instruct the SASL bind to exploit
265 SASL authorization, if available; since connections are cached,
266 this should only be used when authorizing with a fixed identity
267 (e.g. by means of the
272 Otherwise, the default
274 is used, i.e. the proxyAuthz control (Proxied Authorization, RFC 4370)
275 is added to all operations.
277 The supported modes are:
279 \fB<mode> := {legacy|anonymous|none|self}\fP
285 is given, the proxy always authorizes that identity.
286 .B <authorization ID>
293 The former is supposed to be expanded by the remote server according
294 to the authz rules; see
297 In the latter case, whether or not the
299 prefix is present, the string must pass DN validation and normalization.
303 which implies that the proxy will either perform a simple bind as the
305 or a SASL bind as the
307 and assert the client's identity when it is not anonymous.
308 The other modes imply that the proxy will always either perform a simple bind
311 or a SASL bind as the
314 .BR idassert\-authzFrom
315 rules (see below), in which case the operation will fail;
316 eventually, it will assert some other identity according to
318 Other identity assertion modes are
322 which respectively mean that the
329 which means that no proxyAuthz control will be used, so the
333 identity will be asserted.
334 For all modes that require the use of the
336 control, on the remote server the proxy identity must have appropriate
338 permissions, or the asserted identities must have appropriate
340 permissions. Note, however, that the ID assertion feature is mostly
341 useful when the asserted identities do not exist on the remote server.
345 \fBoverride,[non\-]prescriptive,proxy\-authz\-[non\-]critical\fP
349 flag is used, identity assertion takes place even when the database
350 is authorizing for the identity of the client, i.e. after binding
351 with the provided identity, and thus authenticating it, the proxy
352 performs the identity assertion using the configured identity and
353 authentication method.
357 flag is used (the default), operations fail with
358 \fIinappropriateAuthentication\fP
359 for those identities whose assertion is not allowed by the
360 .B idassert\-authzFrom
364 flag is used, operations are performed anonymously for those identities
365 whose assertion is not allowed by the
366 .B idassert\-authzFrom
370 .B proxy\-authz\-non\-critical
371 flag is used (the default), the proxyAuthz control is not marked as critical,
372 in violation of RFC 4370. Use of
373 .B proxy\-authz\-critical
376 The TLS settings default to the same as the main slapd TLS settings,
379 which defaults to "demand".
381 The identity associated to this directive is also used for privileged
382 operations whenever \fBidassert\-bind\fP is defined and \fBacl\-bind\fP
383 is not. See \fBacl\-bind\fP for details.
385 This directive obsoletes
386 .BR idassert\-authcDN ,
387 .BR idassert\-passwd ,
390 .BR idassert\-method .
394 .B idassert-passthru <authz-regexp>
395 if defined, selects what
397 identities bypass the identity assertion feature.
398 Those identities need to be known by the remote host.
401 follows the rules defined for the
408 for details on the syntax of this field.
412 .B idle\-timeout <time>
413 This directive causes a cached connection to be dropped an recreated
414 after it has been idle for the specified time.
417 .B keepalive <idle>:<probes>:<interval>
420 parameter sets the values of \fIidle\fP, \fIprobes\fP, and \fIinterval\fP
421 used to check whether a socket is alive;
423 is the number of seconds a connection needs to remain idle before TCP
424 starts sending keepalive probes;
426 is the maximum number of keepalive probes TCP should send before dropping
429 is interval in seconds between individual keepalive probes.
430 Only some systems support the customization of these values;
433 parameter is ignored otherwise, and system-wide settings are used.
436 .B network\-timeout <time>
437 Sets the network timeout value after which
438 .BR poll (2)/ select (2)
441 returns in case of no activity.
442 The value is in seconds, and it can be specified as for
449 do not return search reference responses.
450 By default, they are returned unless request is LDAPv2.
453 .B noundeffilter <NO|yes>
456 return success instead of searching if a filter is undefined or contains
458 By default, the search is propagated after replacing undefined portions
460 .BR (!(objectClass=*)) ,
461 which corresponds to the empty result set.
464 .B onerr {CONTINUE|stop}
465 This directive allows to select the behavior in case an error is returned
466 by the remote server during a search.
467 The default, \fBcontinue\fP, consists in returning success.
468 If the value is set to \fBstop\fP, the error is returned to the client.
471 .B protocol\-version {0,2,3}
472 This directive indicates what protocol version must be used to contact
474 If set to 0 (the default), the proxy uses the same protocol version
475 used by the client, otherwise the requested protocol is used.
476 The proxy returns \fIunwillingToPerform\fP if an operation that is
477 incompatible with the requested protocol is attempted.
480 .B proxy\-whoami {NO|yes}
481 Turns on proxying of the WhoAmI extended operation. If this option is
482 given, back-ldap will replace slapd's original WhoAmI routine with its
483 own. On slapd sessions that were authenticated by back-ldap, the WhoAmI
484 request will be forwarded to the remote LDAP server. Other sessions will
485 be handled by the local slapd, as before. This option is mainly useful
486 in conjunction with Proxy Authorization.
489 .B quarantine <interval>,<num>[;<interval>,<num>[...]]
490 Turns on quarantine of URIs that returned
491 .IR LDAP_UNAVAILABLE ,
492 so that an attempt to reconnect only occurs at given intervals instead
493 of any time a client requests an operation.
494 The pattern is: retry only after at least
496 seconds elapsed since last attempt, for exactly
498 times; then use the next pattern.
501 for the last pattern is "\fB+\fP", it retries forever; otherwise,
502 no more retries occur.
503 The process can be restarted by resetting the \fIolcDbQuarantine\fP
504 attribute of the database entry in the configuration backend.
507 .B rebind\-as\-user {NO|yes}
508 If this option is given, the client's bind credentials are remembered
509 for rebinds, when trying to re-establish a broken connection,
510 or when chasing a referral, if
516 .B session\-tracking\-request {NO|yes}
517 Adds session tracking control for all requests.
518 The client's IP and hostname, and the identity associated to each request,
519 if known, are sent to the remote server for informational purposes.
520 This directive is incompatible with setting \fIprotocol\-version\fP to 2.
523 .B single\-conn {NO|yes}
524 Discards current cached connection when the client rebinds.
527 .B t\-f\-support {NO|yes|discover}
528 enable if the remote server supports absolute filters
529 (see \fIRFC 4526\fP for details).
532 support is detected by reading the remote server's root DSE.
535 .B timeout [<op>=]<val> [...]
536 This directive allows to set per-operation timeouts.
539 \fB<op> ::= bind, add, delete, modrdn, modify, compare, search\fP
541 The overall duration of the \fBsearch\fP operation is controlled either
542 by the \fBtimelimit\fP parameter or by server-side enforced
543 time limits (see \fBtimelimit\fP and \fBlimits\fP in
546 This \fBtimeout\fP parameter controls how long the target can be
547 irresponsive before the operation is aborted.
548 Timeout is meaningless for the remaining operations,
549 \fBunbind\fP and \fBabandon\fP, which do not imply any response,
550 while it is not yet implemented in currently supported \fBextended\fP
552 If no operation is specified, the timeout \fBval\fP affects all
553 supported operations.
555 Note: if the timelimit is exceeded, the operation is cancelled
556 (according to the \fBcancel\fP directive);
557 the protocol does not provide any means to rollback operations,
558 so the client will not be notified about the result of the operation,
559 which may eventually succeeded or not.
560 In case the timeout is exceeded during a bind operation, the connection
561 is destroyed, according to RFC4511.
563 Note: in some cases, this backend may issue binds prior
564 to other operations (e.g. to bind anonymously or with some prescribed
565 identity according to the \fBidassert\-bind\fP directive).
566 In this case, the timeout of the operation that resulted in the bind
571 .B tls {[try\-]start|[try\-]propagate|ldaps}
574 .B [tls_cacert=<file>]
575 .B [tls_cacertdir=<path>]
576 .B [tls_reqcert=never|allow|try|demand]
577 .B [tls_ciphersuite=<ciphers>]
578 .B [tls_crlcheck=none|peer|all]
580 Specify the use of TLS when a regular connection is initialized. The
581 StartTLS extended operation will be used unless the URI directive protocol
582 scheme is \fBldaps://\fP. In that case this keyword may only be
583 set to "ldaps" and the StartTLS operation will not be used.
584 \fBpropagate\fP issues the StartTLS operation only if the original
586 The \fBtry\-\fP prefix instructs the proxy to continue operations
587 if the StartTLS operation failed; its use is \fBnot\fP recommended.
589 The TLS settings default to the same as the main slapd TLS settings,
592 which defaults to "demand".
596 .B use\-temporary\-conn {NO|yes}
599 create a temporary connection whenever competing with other threads
600 for a shared one; otherwise, wait until the shared connection is available.
602 .SH BACKWARD COMPATIBILITY
603 The LDAP backend has been heavily reworked between releases 2.2 and 2.3,
604 and subsequently between 2.3 and 2.4.
605 As a side-effect, some of the traditional directives have been
606 deprecated and should be no longer used, as they might disappear
610 .B acl\-authcDN "<administrative DN for access control purposes>"
611 Formerly known as the
613 it is the DN that is used to query the target server for acl checking;
614 it is supposed to have read access on the target server to attributes used
615 on the proxy for acl checking.
616 There is no risk of giving away such values; they are only used to
619 .B The acl\-authcDN identity is by no means implicitly used by the proxy
620 .B when the client connects anonymously.
623 feature can be used (at own risk) for that purpose instead.
625 This directive is obsoleted by the
629 when \fIbindmethod\fP=\fBsimple\fP, and will be dismissed in the future.
632 .B acl\-passwd <password>
633 Formerly known as the
635 it is the password used with the above
638 This directive is obsoleted by the
642 when \fIbindmethod\fP=\fBsimple\fP, and will be dismissed in the future.
645 .B idassert\-authcDN "<administrative DN for proxyAuthz purposes>"
646 DN which is used to propagate the client's identity to the target
647 by means of the proxyAuthz control when the client does not
648 belong to the DIT fragment that is being proxied by back-ldap.
649 This directive is obsoleted by the
653 when \fIbindmethod\fP=\fBsimple\fP, and will be dismissed in the future.
656 .B idassert\-passwd <password>
657 Password used with the
660 This directive is obsoleted by the
664 when \fIbindmethod\fP=\fBsimple\fP, and will be dismissed in the future.
667 .B idassert\-mode <mode> [<flags>]
669 .I identity assertion
671 This directive is obsoleted by the
675 and will be dismissed in the future.
678 .B idassert\-method <method> [<saslargs>]
679 This directive is obsoleted by the
683 and will be dismissed in the future.
687 this directive is no longer supported. Use the
689 directive as described above.
692 .B server <hostname[:port]>
693 this directive is no longer supported. Use the
695 directive as described above.
698 .B suffixmassage, map, rewrite*
699 These directives are no longer supported by back-ldap; their
700 functionality is now delegated to the
702 overlay. Essentially, add a statement
706 first, and prefix all rewrite/map statements with
708 to obtain the original behavior.
712 .\" However, to ease update from existing configurations, back-ldap still
713 .\" recognizes them and automatically instantiates the
715 .\" overlay if available and not instantiated yet.
716 .\" This behavior may change in the future.
721 backend does not honor all ACL semantics as described in
722 .BR slapd.access (5).
723 In general, access checking is delegated to the remote server(s).
728 pseudo-attribute and to the other attribute values of the entries
731 operation is honored, which is performed by the frontend.
734 The LDAP backend provides basic proxying functionalities to many overlays.
737 overlay, described in
738 .BR slapo\-chain (5),
741 overlay, described in
742 .BR slapo\-translucent (5),
743 deserve a special mention.
745 Conversely, there are many overlays that are best used in conjunction
746 with the LDAP backend.
749 overlay allows caching of LDAP search requests (queries)
752 .BR slapo\-pcache (5)
756 overlay provides DN rewrite and attribute/objectClass mapping
757 capabilities to the underlying database.
765 default slapd configuration file
768 .BR slapd\-config (5),
770 .BR slapo\-chain (5),
771 .BR slapo\-pcache (5),
773 .BR slapo\-translucent (5),
777 Howard Chu, with enhancements by Pierangelo Masarati
projects / openldap / blob