RE: Fw: ldapadd is failing - error: Naming violation additional info: value of naming attribute 'ou'is not present in entry

["Howard Chu" <hyc@highlandsun.com>]

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Hallvard B
Furuseth

> Raed Nashef writes:
> > I added another ou for "IT Services" as shown below, and that works.
> > It is interesting why it worked with 2.0.23 and does not work with
> > this new version !!!
>
> 'Interesting!!!'?  It was a bug in 2.0.23 that it worked.
> That bug has
> now been fixed, and it returns an error like the LDAP spec says it
> should.

Yes there was a bug, but the correctness of the current behavior is suspect.
In X.511 "Add Entry Arguments" it states

   The entry argument contains the attribute information which, together with
that from the RDN, constitutes the entry to be created.

That is, the directory server should implicitly include the RDN in the set of
attributes in the entry; the RDN does not need to explicitly appear in the
entry body. This was common practice with all the X.500 tools I ever used. In
light of this practice, the real bug was that slapd accepted these inputs but
didn't automatically add the RDN to the stored entry, so it was unavailable
for filter matching, etc.

Sorry, this is probably not a discussion to be having on this list...

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support