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

["Eric Parusel" <lists@globalrelay.net>]

Howard Chu said:
> > '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.

I'm trying to migrate to 2.1.x from 2.0.x, and I've got uid= attributes
that don't match their DN's. :(

I unfortunately can't change the uid attribute values, so there's not
much I can do short of changing the DN's for pretty much every entry...
(and some application logic, sadly)
I was wondering if the following would be sane (below):

Will removing this requirement for my internal LDAP server cause any
problems
with slapd?  Is there anything that "assumes" LDAP entries will be
conformant
to the "correct" behaviour?

--- schema_check.c     Fri Jan 30 15:57:09 2004
+++ schema_check.c     Fri Jan 30 15:57:29 2004
@@ -855,17 +855,19 @@
                                "value of naming attribute '%s' in
unsupported BER form",
                                ava->la_attr.bv_val );
                        rc = LDAP_NAMING_VIOLATION;
                }

+               /*
                if ( value_find( desc, attr->a_vals, &ava->la_value ) != 0 )
{
                        snprintf( textbuf, textlen,
                                "value of naming attribute '%s' is not
present in entry",
                                ava->la_attr.bv_val );
                        rc = LDAP_NAMING_VIOLATION;
                        break;
                }
+               */
        }

        ldap_rdnfree( rdn );
        return rc;
 }


Thanks,
Eric