Douglas Duckworth wrote: > adding new entry "uid=preset,ou=Service Accounts,dc=blah > ldap_add: Object class violation (65) > additional info: invalid structural object class chain > (account/applicationProcess) A directory entry must have a *single* structural object class. While there are usually multiple structural object classes listed only one of them is *the* structural object class. The others are parent object classes of the structural object class. Since 'account' and 'applicationProcess' both directly SUP abstract object class 'top' they count as two distinct structural object classes. > Though this does work as it's now in the LDAP server: > > dn: uid=preset,ou=Service Accounts,dc=blah > objectClass: top > objectClass: account > objectClass: applicationProcess > objectClass: simpleSecurityObject It's invalid and you might run into issues modifying this entry later. You should choose either 'account' or 'applicationProcess'. BTW: It should normally not be possible to add such entry. How did you add it? With slapadd or by using Relax Rules Control? Ciao, Michael.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature