[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
back-sql and multiple objectclasses
- To: openldap-software@openldap.org
- Subject: back-sql and multiple objectclasses
- From: Wilhelm Meier <wilhelm.meier@fh-kl.de>
- Date: Thu, 28 Jun 2007 10:13:34 +0200
- Content-disposition: inline
- Organization: Fachhochschule Kaiserslautern / ZweibrÃcken
- User-agent: KMail/1.9.5
Hi,
I have a problem using back-sql and entries with multiple object classes:
If I add the entry:
dn: cn=testuser2,dc=kmux,dc=de
cn: testuser2
sn: test
objectClass: top
objectClass: person
objectClass: posixAccount
gidNumber: 514
uidNumber: 4711
uid: test2
homeDirectory: hh
I get in the logs of slapd complains that attr uidNumber in objectClass person
is undefined. That's right, but the object has the additional class
posixAccount, which has the attribute.
When I look in the logs, I see that the table ldap_entry_objectclasses gets
inserted the auxiliary class posixAccount AFTER it tries to set the attribute
uidNumber. So ist clear that it doen't find the attribute.
The tables in the database are constructed similar to the objectclasses.
Any hints?
--
Wilhelm