directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <>
Subject [jira] Commented: (DIREVE-230) Deletion of RDN and objectClass attribute
Date Tue, 23 Aug 2005 17:28:08 GMT
    [ ] 

Alex Karasulu commented on DIREVE-230:

I think this is all a result of not having proper schema checking in place.  If the server
checked to make sure a modify operation left a valid structural objectClass in place after
all mods are applied then we would not have this problem.  Likewise we should not allow the
deletion of the RDN attributes without an RDN change.  Overall schema checking is a mess we
really need a central strategy behind it.  For now I will add schema checks to make sure these
consistency issues do not arrise.

> Deletion of RDN and objectClass attribute
> -----------------------------------------
>          Key: DIREVE-230
>          URL:
>      Project: Directory Server
>         Type: Bug
>     Versions: 0.9.2
>     Reporter: Stefan Zoerner
>     Assignee: Alex Karasulu
>  Attachments:
> It is possible to remove the RDN and the objectClass attribute from an entry via a modify
operation. Removing the objectClass attribute leads to an entry which can't be deleted.
> Attached you find a testcase which demonstrates the deletion of the objectClass on a
person entry.
> After this operation, it is still possible to lookup the entry with its DN, although
it has no attributes and deletion attempts cause an error: 
> LDAP: error code 54 - failed to delete entry cn=Charly Brown,dc=apache,dc=org

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message