Re: slapcat output from 2.0.21 to slapadd to openldap-2.3.24

[Aaron Richton <richton@nbcs.rutgers.edu>]

> dn: o=HotCoco, c=US
> o: HotCoco.com
> objectClass: organization

> When I changed the "o: HotCoco.com" to "o: HotCoco", the error (value
> of naming attribute 'o' is not present in entry) went away, and
> ldapadd worked.
>
> Can you please explain why this is the case?

Well, they have to match. If you want to have
o: HotCoco.com then you need dn: o=HotCoco.com, c=US

Given your dn: o=HotCoco, c=US you need o: HotCoco. because they match.


Personally, I'd recommend cleaning up the data on your RH7 box (i.e. 
ldapmodify your bogus entry above) to the point where you can slapadd to 
2.3.24 cleanly. Once you've got sane data, cut over to the new server, 
which will also more strictly enforce the relevant standards and not let 
an entry like that in again. This would be a lot safer than continuing to 
run with 2.0.21 and letting users get away with more bogus entries.