[Date Prev][Date Next]
Re: ldapadd problem
I use sambaAccount and inetOrgPerson together all the time in Openldap 2.0.27
and 2.1.25 without problems. I'm using the unmodified schema files as
distributed by the OpenLDAP and Samba teams, plus a site-local schema and the
lachman sendmail schema. The samba schema I'm using are from 2.2 and 3.x,
respectively (note these versions are very different).
I structured my use of objectclasses for 2.1.25 by a brute-force trial and
error method involving some very silly gawk commands. I can't say I really
understand why I use the ones I do, I just found the minimum number of
objectclasses needed to support the attributes I required. It was the least-
cost path for me at the time; I apologize for the lack of intellectual effort!
My objectclasses for accounts in the "people" ou are (in order):
On 17 Feb 2004 at 14:26, Tony Earnshaw wrote:
> tir, 17.02.2004 kl. 13.31 skrev Galoppin Fabian:
> > adding new entry "uid=phc,ou=People,dc=test,dc=be"
> > ldapadd: update failed: uid=phc,ou=People,dc=test,dc=be
> > ldap_add: Object class violation (65)
> > additional info: invalid structural object class
> > chain (sambaAccount/inetOrgPerson)
> It's simply telling you you can't have both sambaAccount and
> inetOrgPerson. Leave one of them out.