Hi, If I add following ldif with slapadd(attribute 'ou' and 'ou' in dn: are different): dn: ou=testou.auto,dc=my-domain,dc=com ou: testou.misc objectClass: top objectClass: organizationalUnit
Slapadd doesn't evalute it as an error in ldif but it adds 'ou' from dn as another attribute. Added entry then looks like: # testou.auto, my-domain.com dn: ou=testou.auto,dc=my-domain,dc=com ou: testou.misc ou: testou.auto objectClass: top objectClass: organizationalUnit
Is this expected behavior or a bug? Tested with openldap-2.4.39
On 05/19/2014 01:21 PM, David Spurek wrote:
Hi, If I add following ldif with slapadd(attribute 'ou' and 'ou' in dn: are different): dn: ou=testou.auto,dc=my-domain,dc=com ou: testou.misc objectClass: top objectClass: organizationalUnit
Slapadd doesn't evalute it as an error in ldif but it adds 'ou' from dn as another attribute. (...) Is this expected behavior or a bug?
Expected. RFC 4511 section 4.7 (Add Operation) mentions:
- attributes: the list of attributes that, along with those from the RDN, make up the content of the entry being added. Clients MAY or MAY NOT include the RDN attribute(s) in this list.
Older LDAP versions said the opposite, that the Add request should fail.
openldap-technical@openldap.org