MAN page from StartCom 5 openldap-servers-overlays-2.3.43-12.SEL5_5.i386.rpm
Section: File Formats (5)
slapo-dynlist - Dynamic List overlay
(8)allows expansion of dynamic groups and more.Any time an entry with a specific objectClass is being returned,the LDAP URI-valued occurrences of a specific attribute areexpanded into the corresponding entries, and the valuesof the attributes listed in the URI are added to the originalentry.No recursion is allowed, to avoid potential infinite loops.The resulting entry must comply with the LDAP data model, so constraintsare enforced.For example, if a SINGLE-VALUE
attribute is listed,only the first value results in the final entry.The above described behavior is disabled when the manageDSAit
control (RFC 3296) is used.In that case, the contents of the dynamic group entry is returned;namely, the URLs are returned instead of being expanded.
The config directives that are specific to thedynlist
overlay must be prefixed bydynlist-
,to avoid potential conflicts with directives specific to the underlying database or to other stacked overlays.
- overlay dynlist
- This directive adds the dynlist overlay to the current database,or to the frontend, if used before any database instantiation; seeslapd.conf(5)for details.
Thisslapd.confconfiguration option is define for the dynlist overlay. It may have multiple occurrences, and it must appear after theoverlaydirective.
- dynlist-attrset <group-oc> <URL-ad> [<member-ad>]
- The value <group-oc> is the name of the objectClass that triggers the dynamic expansion of thedata.
The value<URL-ad>is the name of the attributeDescription that contains the URI that is expanded by the overlay; if none is present, no expansion occurs.If the intersection of the attributes requested by the search operation (or the asserted attribute for compares) and the attributes listed in the URI is empty, no expansion occurs for that specific URI.It must be a subtype of labeledURI.
The value<member-ad>is optional; if present, the overlay behaves as a dynamic group: thisattribute will list the DN of the entries resulting from the internal search.In this case, the <attrs> portion of the URI must be absent, and the DNs of all the entries resulting from the expansion of the URI are listedas values of this attribute.Compares that assert the value of the<member-ad>attribute of entries with <group-oc>objectClass apply as if the DN of the entries resulting from the expansion of the URI were present in the <group-oc> entry as values of the<member-ad>attribute.
The dynlist overlay may be used with any backend, but it is mainly intended for use with local storage backends.In case the URI expansion is very resource-intensive and occurs frequentlywith well-defined patterns, one should consider adding a proxycachelater on in the overlay stack.
This example collects all the email addresses of a database into a singleentry; first of all, make sure that slapd.conf contains the directives:
include /path/to/dyngroup.schema # ... database <database> # ... overlay dynlist dynlist-attrset groupOfURLs memberURL
and that slapd loads dynlist.la, if compiled as a run-time module;then add to the database an entry like
dn: cn=Dynamic List,ou=Groups,dc=example,dc=com objectClass: groupOfURLs cn: Dynamic List memberURL: ldap:///ou=People,dc=example,dc=com?mail?sub?(objectClass=person)
If no <attrs> are provided in the URI, all (non-operational) attributes arecollected.
This example implements the dynamic group feature on the memberattribute:
include /path/to/dyngroup.schema # ... database <database> # ... overlay dynlist dynlist-attrset groupOfURLs memberURL member
- default slapd configuration file
(5)overlay supports dynamic configuration viaback-config
This module was written in 2004 by Pierangelo Masarati for SysNet s.n.c.
- SEE ALSO
This document was created byman2html,using the manual pages.