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 \fIadd\fP, \fImodify\fP and \fIrename\fP commands
21 and only seeks to control the \fIadd\fP and \fIreplace\fP values
22 of \fImodify\fP and \fIrename\fP requests.
26 option applies to the constraint overlay.
27 It should appear after the
31 .B constraint_attribute <attribute_name>[,...] <type> <value> [<extra> [...]]
32 Specifies the constraint which should apply to the comma-separated
33 attribute list named as the first parameter.
34 Two types of constraint are currently supported -
42 The parameter following the
44 type is a Unix style regular expression (See
46 ). The parameter following the
48 type is an LDAP URI. The URI will be evaluated using an internal search.
49 It must not include a hostname, and it must include a list of attributes
52 The parameter following the
54 type is a string that is interpreted according to the syntax in use
55 for ACL sets. This allows to construct constraints based on the contents
60 type can be used to enforce a limit on an attribute length, and the
62 type limits the number of values of an attribute.
64 Extra parameters can occur in any order after those described above.
67 .B <extra> : restrict=<uri>
71 This extra parameter allows to restrict the application of the corresponding
72 constraint only to entries that match the
77 portions of the LDAP URI.
80 if present, must be within the naming context of the database.
85 is present; it defaults to
87 The other parameters of the URI are not allowed.
91 Any attempt to add or modify an attribute named as part of the
92 constraint overlay specification which does not fit the
93 constraint listed will fail with a
94 LDAP_CONSTRAINT_VIOLATION error.
100 constraint_attribute jpegPhoto size 131072
101 constraint_attribute userPassword count 3
102 constraint_attribute mail regex ^[:alnum:]+@mydomain.com$
103 constraint_attribute title uri
104 ldap:///dc=catalog,dc=example,dc=com?title?sub?(objectClass=titleCatalog)
105 constraint_attribute cn,sn,givenName set
106 "(this/givenName + [ ] + this/sn) & this/cn"
107 restrict="ldap:///ou=People,dc=example,dc=com??sub?(objectClass=inetOrgPerson)"
111 A specification like the above would reject any
113 attribute which did not look like
114 .BR "<alpha-numeric string>@mydomain.com" .
115 It would also reject any
117 attribute whose values were not listed in the
121 entries in the given scope.
122 Finally, it requires the values of the attribute
124 to be constructed by pairing values of the attributes
128 separated by a space, but only for entries derived from the objectClass
134 default slapd configuration file
138 This module was written in 2005 by Neil Dunbar of Hewlett-Packard and subsequently
139 extended by Howard Chu and Emmanuel Dreyfus.