1 .TH SLAPO-DYNLIST 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 1998-2005 The OpenLDAP Foundation, All Rights Reserved.
3 .\" Copying restrictions apply. See the COPYRIGHT file.
6 slapo-dynlist \- Dynamic List overlay
14 allows expansion of dynamic groups and more.
15 Any time an entry with a specific objectClass is being returned,
16 the LDAP URI-valued occurrences of a specific attribute are
17 expanded into the corresponding entries, and the values
18 of the attributes listed in the URI are added to the original
20 No recursion is currently allowed, to avoid potential infinite loops.
23 The config directives that are specific to the
25 overlay must be prefixed by
27 to avoid potential conflicts with directives specific to the underlying
28 database or to other stacked overlays.
32 This directive adds the dynlist overlay to the current database,
33 or to the frontend, if used before any database instantiation; see
40 configuration options apply to the dynlist overlay. They must appear
45 .B dynlist-oc <objectClass>
46 The name of the objectClass that triggers the dynamic expansion of the
47 data. This statement is required.
49 .B dynlist-ad <attributeName>
50 The name of the attributeDescription that holds the LDAP URI values that
51 will expand; if none is present, no expansion occurs. If the intersection
52 of the attributes requested by the search operation (or the asserted attribute
53 for compares) and the attributes listed in the URI is empty, no expansion
54 occurs for that specific URI. This statement is required.
56 .B dynlist-member-ad <attributeName>
57 The name of the attributeDescription that will list the DN of the entries
58 resulting from the internal search. This statement is optional and, if
59 present, changes the behavior of the overlay into that of a dynamic group.
60 The <attrs> portion of the URI is ignored, and the DNs of all the entries
61 resulting from the expansion of the URI are listed as values of this
65 The dynlist overlay may be used with any backend, but it is mainly
66 intended for use with local storage backends.
67 In case the URI expansion is very resource-intensive and occurs frequently
68 with well-defined patterns, one should consider adding a proxycache
69 later on in the overlay stack.
72 This example collects all the email addresses of a database into a single
73 entry; first of all, make sure that slapd.conf contains the directives:
77 include /path/to/dyngroup.schema
84 dynlist-oc groupOfURLs
88 and that slapd loads dynlist.la, if compiled as a run-time module;
89 then add to the database an entry like
92 dn: cn=Dynamic List,ou=Groups,dc=example,dc=com
93 objectClass: groupOfURLs
95 memberURL: ldap:///ou=People,dc=example,dc=com?mail?sub?(objectClass=person)
98 If no <attrs> are provided in the URI, all (non-operational) attributes are
105 default slapd configuration file
111 This module was written in 2004 by Pierangelo Masarati for SysNet s.n.c.