Jack Emmerichs wrote: > We are upgrading from OpenLDAP 2.2.29 to the current 2.3.32. The build > seems to work, and the basic database structure seems okay and displays > as: > > # extended LDIF > # > # LDAPv3 > # base <dc=my-domain,dc=com> with scope subtree > # filter: (objectclass=*) > # requesting: ALL > # > > # my-domain.com > dn: dc=my-domain,dc=com > dc: my-domain > objectClass: top > objectClass: dcObject > objectClass: organization > o: OrgName > > # people, my-domain.com > dn: ou=people,dc=my-domain,dc=com > ou: people > objectClass: top > objectClass: organizationalUnit > > # Manager, my-domain.com > dn: cn=Manager,dc=my-domain,dc=com > objectClass: organizationalRole > cn: Manager > > # search result > search: 2 > result: 0 Success > > > The problem is that I cannot find a syntax for posixAccount entries the > LDAP will accept without throwing an error such as: > > LDAP error code 21 - objectClass: value #1 invalid per syntax > > The ldif format exported by the old version looks like this (it's a > Windows system with dummy data for Unix items uid#, gid#, homeDirectory, > etc.): > > > dn: cn=AWS User 1,ou=people, dc=my-domain,dc=com > gidNumber: 100 > userPassword:: e1NIQX1pK1BKUTdGZ24vKy94UnF0Wm0wS0JLMzRQSjA9 > uidNumber: 100 > uid: awsuser1 > objectClass: top > objectClass: account > objectClass: posixAccount > homeDirectory: notUsed > cn: AWS User 1 > > I've looked at and tried lots of examples containing from 3 to 5 > objectClass entries, but I always get the same error on some objectClass > value #. > > Questions: > Is this in fact an improper definition for posixAccount? If so, what > should we use instead? > > Are there any known restrictions using OpenLDAP that would make it reject > this entry if it is not an error? > > Thanks for any help that anyone can offer. >
See http://ldap.akbkhome.com/index.php/objectclass/posixAccount.html -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E [EMAIL PROTECTED] Open Source. Open Solutions(tm). http://www.suretecsystems.com/ --- You are currently subscribed to [EMAIL PROTECTED] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
