Re: Invalid Structural Object Class Chain (account/person)

[Buchan Milne <bgmilne@obsidian.co.za>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Thomas wrote:
| I'm attempting to populate our LDAP database and I plan on using it for
| both authorization and as a corporate address book.  When I attempt to
| import the LDIF file I get the following.
|
| ldapadd -a -W -x -D "cn=Manager,dc=anc.net,dc=anci" -f pwthoma.ldif
| Enter LDAP Password:
| adding new entry "uid=A0971217/-2663,ou=People,dc=anc.net,dc=anci"
| ldapadd: update failed: uid=A0971217/-2663,ou=People,dc=anc.net,dc=anci
| ldap_add: Object class violation (65)
| additional info: invalid structural object class chain (account/person)
|

There have been other answers, but I don't think any mentioned that the
account objectclass (AFAIK only used by pam_ldap) is deprecated, and if
you need the host attribute, you should use the auxiliary objectclass
hostObject defined in the ldapns.schema provided with newer pam_ldap
versions

Regards,
Buchan

- --
Buchan Milne                      Senior Support Technician
Obsidian Systems                  http://www.obsidian.co.za
B.Eng                                RHCE (803004789010797)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAyJMcrJK6UGDSBKcRAmFoAKDAzeYdKyYvyioPdx+1xZzYUS2JsACfbiDU
TcgKjOgIT2SIKF6T8t6Nwrk=
=dGqW
-----END PGP SIGNATURE-----