Re: objectclass: value #0 invalid per syntax - no trailing spaces however

[Greg Matthews <gmatt@nerc.ac.uk>]

On Tue, 2004-11-09 at 15:40, Bill and Calanite Logan wrote:
> ## FIRST Level hierarchy - people
> # this is an ENTRY sequence and is preceded by a BLANK line
> 
> dn: ou=people, dc=localhost
> ou: people
> description: All people in organisation
> objectClass: inetOrgPerson

this looks odd. ObjectClass inetOrgPerson is usually used to describe a
person/user object. here you seem to be using it to describe an
organizationalUnit, is this what you intended? However, this is possible
as the objectclass organizationalperson can contain the attribute ou but
this is a hierarchy person->organizationalperson->inetorgperson and
"person" has *required attributes* sn and cn. Therefore you can't add
the object above, with objectclass inetorgperson, unless you also
include the attributes cn and sn, otherwise you are breaking the schema.
The same applies to the second level entry.

GREG

> 
> ## SECOND Level hierarchy - people entries
> # this is an ENTRY sequence and is preceded by a BLANK line
> 
> dn: cn=Joe Schmo,ou=people,dc=localhost
> objectclass: inetOrgPerson
> cn: Joe Schmo
> sn: Schmo
> uid: jschmo
> mail: joe@mydomain.com
> mail: r.schmo@mydomain.com
> ou: sales
> 
> returns this error code:
> 
> adding new entry "dc=localhost"
> ldap_add: Already exists (68)
> 
> adding new entry "ou=people, dc=localhost"
> ldap_add: Invalid syntax (21)
>         additional info: objectClass: value #0 invalid per syntax
> 
> adding new entry "cn=Joe Schmo,ou=people,dc=localhost"
> ldap_add: Invalid syntax (21)
>         additional info: objectclass: value #0 invalid per syntax
> 

> Bill Logan
-- 
Greg Matthews
iTSS Wallingford	01491 692445