[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Entry

I'm guessing it's the 'o: penguin206'.  by default, none
of the objectclasses you have specified allow for the
'o' attribrute...  Can't tell you why other things let
you get away with it... is schema checking off?


Quoting dclement@mines.edu:

> When I insert the following ldif file, it returns the
error  `Object class
> violation', however, when I insert the same data
through any other
> interface,
> it works correctly.  This leads me to suspect that the
problem lies within
> the
> LDIF file, however, I have been unable to locate an
error.  Any
> help/spotchecking would be greatly appreciated.
> I am running the latest build of OpenLDAP.
> dn: cn=Jed E. Diem, o=penguin206
> o: penguin206
> cn: Jed E. Diem
> sn: Diem
> uid: jed
> title: Richardson
> userPassword: {SHA}_____________________
> objectclass: top
> objectclass: person
> objectclass: organizationalPerson
> Sincerely,
> David Hartwell Clements
> Information Systems Specialist
> Tulane University, TIS