François Beretti a écrit :
you MUST provide a structural objectclass, like 'inetOrgPerson' for example, which turn your example to :
dn: uid=tarkhil, dc=sub, dc=ru objectClass: shadowAccount objectClass: inetOrgPerson uid: tarkhil
ooops
Regards, François
François
[12:37] server:/tmp # ldapadd -D "cn=Manager,dc=sub,dc=ru" -w password dn: cn=test2, dc=sub, dc=ru objectClass: posixGroup cn: test2 gidNumber: 1024
adding new entry "cn=test2, dc=sub, dc=ru"
As far as I understand man ld_errno, in the first example slapd complaints:
LDAP_OBJECT_CLASS_VIOLATION
An object class violation occurred (e.g., a "must"
attribute was missing from the entry).
but I cannot understand what exactly the problem is.
The same setup worked quite well on openldap 2.0...