[Date Prev][Date Next]
Re: err=20 when rdn attr name is different that attr name in object (ITS#1997)
The "two version" simply differ by case. This should be handled properly
There is no schema awareness in this client; all it knows are strings. I
assure you it is not changing any strings into other strings, and the case
difference is what is being detected as a "different attribute". This does
not sound to me like a client bug. Do you want a netcat filter, a higher
level openldap log? I can assure you I do not have multiple instances of
the same attribute that vary by anything but case.
Quoting "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>:
> At 10:10 AM 2002-08-07, email@example.com wrote:
> >I was using JNDI interface from Java. When DN used mixed case in RDN
> >attribute name in object was all lower, got err=20. Changed RDN attr to
> >all lower case and problem was fixed.
> So, it's not an ldapadd(1) bug but a JNDI bug (or one in your
> JNDI application).
> The client is sending a malformed LDAP Add Request PDU.
> The client generated PDU includes two versions of the
> same attribute in violation of the protocol and its data
> model. The client should be fixed.
> >This exact code worked fine w/ 2.0.18, and only flared up when I
> >to 2.1.2.
> Yes, we fixed a number of bugs which unintentionally
> allowed non-standard behavior.
This mail sent from Biltmore Communications