Re: err=20 when rdn attr name is different that attr name in object (ITS#1997)

[kmccarthy@senets.com]

I was using JNDI interface from Java. When DN used mixed case in RDN and 
attribute name in object was all lower, got err=20. Changed RDN attr to 
all lower case and problem was fixed.

This exact code worked fine w/ 2.0.18, and only flared up when I upgraded 
to 2.1.2. I can get you log file, but all it says it attribute provided 
more than once. If there is a log level that would be of more use I'll 
trap for you.

Kevin

Quoting "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>:

> At 12:48 PM 2002-07-30, kevin@kogz.com wrote:
> >Full_Name: Kevin McCarthy
> >Version: 2.1.3
> >OS: Linux
> >URL: ftp://ftp.openldap.org/incoming/
> >Submission from: (NULL) (67.105.66.160)
> >
> >
> >When the RDN attribute name case differs from the case of the attribute
> name
> >inside the object body, err=20 (attribute 'XXX' provided more than
> once) is
> >thrown.
> 
> The case of the RDN attribute name is irrelevant to
> this error message.  I confirmed this though testing.
> 
> This error occurs when the entry contains the same
> attribute more than once.
> 
> I suspect you have another problem, such as providing
> malformed LDIF to ldapadd(1).
> 
> >Example:
> >
> >DN: userName=kevin, ou=people, dc=test, dc=com
> >username: kevin
> >objectclass: person
> >...
> >
> >[LDAP: error code 20 - attribute 'userName' provided more than once]
> >
> >ldapadd should be smart enough to detect this case and accept the
> entry,
> >especially since certain client map all DNs TO UPPER CASE.
> 
> 




-------------------------------------------------
This mail sent from Biltmore Communications
	http://www.biltmorecomm.com