directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Zoerner (JIRA)" <>
Subject [jira] Commented: (DIREVE-230) Deletion of RDN and objectClass attribute
Date Tue, 23 Aug 2005 20:59:09 GMT
    [ ] 

Stefan Zoerner commented on DIREVE-230:

I refined my test cases according to Alex cite from RFC 2251. After this I found out that
some servers provide other return codes, at least if the the removal is tried on a part of
the RDN which is a required attribute as well (e.g. cn for person).

Sun JS DS 5.2: 65 - Object Class Violation
OpenLDAP 2.1: 64 - Naming Violation
IBM Tivoli 6.0: 67 - Not Allowed On RDN (at last)
MS ADAM: 67 - Not Allowed On RDN (inventive message text here: "CANT_ON_RDN")

I will therefor accept all three values in my test cases in order to keep the bar green for
each solution. The 67 seems to be the better choice than 64, although it may depend on the
fact that I used a required attribute as a RDN. The Sun server may check schema violations
first, therfore its message is reasonable as well. Anyway, I will also add a test with a non
required attribute as RDN.

> 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
>      Fix For: 0.9.2
>  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