1 .TH SLAPO-CONSTRAINT 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2 .\" Copyright 2005-2006 Hewlett-Packard Company
3 .\" Copyright 2006-2008 The OpenLDAP Foundation All Rights Reserved.
4 .\" Copying restrictions apply. See COPYRIGHT/LICENSE.
7 slapo-constraint \- Attribute Constraint Overlay to slapd
11 The constraint overlay is used to ensure that attribute values match
12 some constraints beyond basic LDAP syntax. Attributes can
13 have multiple constraints placed upon them, and all must be satisfied
14 when modifying an attribute value under constraint.
16 This overlay is intended to be used to force syntactic regularity upon
17 certain string represented data which have well known canonical forms,
18 like telephone numbers, post codes, FQDNs, etc.
20 It constrains only LDAP adds and modify commands and only seeks to
21 control the add and modify value of a modify request.
25 option applies to the constraint overlay.
26 It should appear after the
30 .B constraint_attribute <attribute_name>[,...] <type> <value> [<extra> [...]]
31 Specifies the constraint which should apply to the comma-separated
32 attribute list named as the first parameter.
33 Two types of constraint are currently supported -
41 The parameter following the
43 type is a Unix style regular expression (See
45 ). The parameter following the
47 type is an LDAP URI. The URI will be evaluated using an internal search.
48 It must not include a hostname, and it must include a list of attributes
51 The parameter following the
53 type is a string that is interpreted according to the syntax in use
54 for ACL sets. This allows to construct constraints based on the contents
59 type can be used to enforce a limit on an attribute length, and the
61 type limits the number of values of an attribute.
63 Extra parameters can occur in any order after those described above.
66 .B <extra> : restrict=<uri>
70 This extra parameter allows to restrict the application of the corresponding
71 constraint only to entries that match the
76 portions of the LDAP URI.
79 if present, must be within the naming context of the database.
84 is present; it defaults to
86 The other parameters of the URI are not allowed.
90 Any attempt to add or modify an attribute named as part of the
91 constraint overlay specification which does not fit the
92 constraint listed will fail with a
93 LDAP_CONSTRAINT_VIOLATION error.
99 constraint_attribute jpegPhoto size 131072
100 constraint_attribute userPassword count 3
101 constraint_attribute mail regex ^[:alnum:]+@mydomain.com$
102 constraint_attribute title uri
103 ldap:///dc=catalog,dc=example,dc=com?title?sub?(objectClass=titleCatalog)
104 constraint_attribute cn,sn,givenName set
105 "(this/givenName + [ ] + this/sn) & this/cn"
106 restrict="ldap:///ou=People,dc=example,dc=com??sub?(objectClass=inetOrgPerson)"
110 A specification like the above would reject any
112 attribute which did not look like
113 .BR "<alpha-numeric string>@mydomain.com" .
114 It would also reject any
116 attribute whose values were not listed in the
120 entries in the given scope.
121 Finally, it requires the values of the attribute
123 to be constructed by pairing values of the attributes
127 separated by a space, but only for entries derived from the objectClass
133 default slapd configuration file
137 This module was written in 2005 by Neil Dunbar of Hewlett-Packard and subsequently
138 extended by Howard Chu and Emmanuel Dreyfus.