changed notes changed state Open to Test moved from Incoming to Software Bugs
Full_Name: Version: 2.4.38 OS: URL: Submission from: (NULL) (212.227.35.93) Sometimes it's useful to restrict an existing attribute type declared multi-valued to a single value with slapo-constraint to avoid modifying the standard schema. Example: constraint_attribute uid count 1 restrict="ldap:///ou=example??sub?(objectClass=account)" Unfortunately when using uid in the RDN one cannot rename the entry anymore even when deleteoldrdn is set to true. slapo-constraint should handle this case exactly like SINGLE-VALUE RDN attributes are handled.
On 12/28/2013 01:52 PM, michael@stroeder.com wrote: > Full_Name: > Version: 2.4.38 > OS: > URL: > Submission from: (NULL) (212.227.35.93) > > > Sometimes it's useful to restrict an existing attribute type declared > multi-valued to a single value with slapo-constraint to avoid modifying the > standard schema. > > Example: > > constraint_attribute > uid > count 1 > restrict="ldap:///ou=example??sub?(objectClass=account)" > > Unfortunately when using uid in the RDN one cannot rename the entry anymore even > when deleteoldrdn is set to true. > > slapo-constraint should handle this case exactly like SINGLE-VALUE RDN > attributes are handled. Should be fixed in git master. Nothing specific to rename; rather, slapo-constraint was not handling internal modifications like softadd/softdel. p. -- Pierangelo Masarati Associate Professor Dipartimento di Scienze e Tecnologie Aerospaziali Politecnico di Milano
changed notes changed state Test to Release
changed notes changed state Release to Closed
fixed in master fixed in RE25 fixed in RE24