1833437 Members
3452 Online
110052 Solutions
New Discussion

HPUX & OpenLDAP

 
Phil Daws_2
Regular Advisor

HPUX & OpenLDAP

Hi:

I have successfully compiled and installed OpenLDAP on HPUX 11i. I would like to use the nis.schema so that we can integrate LDAP and PAM. I have attached a copy of our slapd.conf file.

When I try and add a entry to the server I get the following errors :

adding new entry "uid=ldaptest,ou=People,dc=unix,dc=dcfs-uk-int,dc=com"
ldap_add: No such object
additional info: parent does not exist

ldif_record() = 32

In the LDIF I have the following information :

dn: uid=ldaptest,ou=People,dc=unix,dc=dcfs-uk-int,dc=com
uid: ldaptest
cn: LDAP Test User
objectClass: top
objectClass: account
objectClass: posixAccount
userPassword: {crypt}*
loginShell: /bin/ksh
uidNumber: 6000
gidNumber: 20
homeDirectory: /home/ldaptest
gecos: LDAP Test User, Development

Any ideas what I am doing wrong?
3 REPLIES 3
Steven Gillard_2
Honored Contributor

Re: HPUX & OpenLDAP

Its telling you the parent entry is missing (most likely the ou=People entry).

Try adding the following entry to the start of your ldif file:

dn: ou=People,dc=unix,dc=dcfs-uk-int,dc=com
ou: People
cn: UNIX users accounts
objectClass: top
objectClass: organizationalUnit

If that still fails have a closer read of the administrators guide:

http://www.openldap.org/doc/admin/index.html

Particularly chapter 7 which deals with database creation.

Regards,
Steve
Phil Daws_2
Regular Advisor

Re: HPUX & OpenLDAP

I now get the following :(

adding new entry "ou=People,dc=unix,dc=dcfs-uk-int,dc=com "
ldap_add: Invalid syntax
additional info: objectClass: value #0 invalid per syntax

ldif_record() = 21
Steven Gillard_2
Honored Contributor

Re: HPUX & OpenLDAP

Oops, my mistake, its been a few months since I played with this stuff - the organizationalUnit object class does not have a 'common name' or cn attribute. Remove this line from the ou=People entry so you have:

dn: ou=People,dc=unix,dc=dcfs-uk-int,dc=com
ou: People
objectClass: top
objectClass: organizationalUnit

You can add a 'description' attribute instead if you like. RFC 2256 describes all these classes and attributes if you need more detail.

Regards,
Steve