[Date Prev][Date Next]
restriction for structural objectclass?
- To: openldap-software@OpenLDAP.org
- Subject: restriction for structural objectclass?
- From: Andreas Gabriel <firstname.lastname@example.org>
- Date: Sun, 05 Oct 2003 12:48:36 +0200
- Organization: Philipps Universitaet Marburg
- User-agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624
I don't understand the new restrictions (openLDAP 2.1.22) for changing
the structural objectclass of an entry.
1. to make a copy of the entry
2. to delete the entry
3. to change the structural objectclass of the copy
4. to re-add the changed copy of the entry
isn't very useful for following reasons:
Changing the root's structural objectclass of a DN tree.
You must first export/delete all DN's of the root and the root itself;
make your changes and re-add all DNs (very exhausting and
unusable for interactive clients as gq and web interfaces)
If many admins are able to add new
users (DNs) to LDAP from differnt clients, you need a locking mechanism.
With our WEB-Interface (developed for version 2.0.x)
we add first a new DN with a generic structural ObjectClass
and the auxiliary extensibleObject class. At this moment nobody else
from another client can add a new DN with same denotation (e.g. username).
After the admin has added all new data, the new data is commited to LDAP, but
also the generic objectclass is changed (e.g. into inetPerson). Since 2.1.x this
is apparently no longer possible. The rule to delete first the entry and to re-add
the changed entry completely cancels the locking!!
Any suggestions and comments?
-- Andreas Gabriel
@AG Neurophysik ,Renthof 7, 35032 Marburg TEL/FAX +49 +6421 28-25683/27034
@HRZ, Hans-Meerwein-Str. , 35032 Marburg TEL/FAX +49 +6421 28-23560/26994
------------------ Philipps-Universitaet Marburg -------------------------