Full_Name: Christopher Dyck Version: 2.4.11 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (130.83.183.3) I found a strange behavior in the unique overlay. unique overlay only works, when a rootdn is specified in the slapd.conf, because the unique_search function uses the rootdn for searching. (took me hours to determine why my configuration didn't do it's job) Isn't it more reasonable to use the dn with which the add or modify is performed? Or mention this circumstance at least in the manpage?!
mfn@fs-etit.de wrote: > Full_Name: Christopher Dyck > Version: 2.4.11 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (130.83.183.3) > > > I found a strange behavior in the unique overlay. > > unique overlay only works, when a rootdn is specified in the slapd.conf, because > the unique_search function uses the rootdn for searching. (took me hours to > determine why my configuration didn't do it's job) > > Isn't it more reasonable to use the dn with which the add or modify is > performed? Definitely not. The user performing the write may not have sufficient access to see all of the instances of the attribute in question. > Or mention this circumstance at least in the manpage?! Probably. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
changed notes changed state Open to Test moved from Incoming to Documentation
changed notes changed state Test to Release
changed notes changed state Release to Closed
fixed in HEAD fixed in RE24