You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Zoerner (JIRA)" <di...@incubator.apache.org> on 2006/01/10 17:07:22 UTC

[jira] Closed: (DIREVE-268) Adding a duplicate attribute value should cause an error.

     [ http://issues.apache.org/jira/browse/DIREVE-268?page=all ]
     
Stefan Zoerner closed DIREVE-268:
---------------------------------


I have retested this one with a current 0.9.4 snapshot. Both situations described in the test cases worked as expected. Nice to see that, and in my role as the reporter, I close this issue: Click.

> Adding a duplicate attribute value should cause an error.
> ---------------------------------------------------------
>
>          Key: DIREVE-268
>          URL: http://issues.apache.org/jira/browse/DIREVE-268
>      Project: Directory Server
>         Type: Bug
>     Versions: 0.9.3
>     Reporter: Stefan Zoerner
>     Assignee: Alex Karasulu
>     Priority: Minor
>      Fix For: 0.9.4
>  Attachments: ModifyAddDuplicateValueTest.java
>
> Adding a duplicate attribute value to an entry with a single modify operation results in an invalid entry. After the operation it contains the parameter value twice. Hence someone is able to change this entry
> dn: cn=Heather Nova,ou=system
> objectClass: top
> objectClass: person
> cn: Heather Nova
> sn: Nova
> into an entry which looks like this:
> dn: cn=Heather Nova,ou=system
> objectClass: top
> objectClass: person
> objectClass: organizationalPerson
> objectClass: organizationalPerson
> cn: Heather Nova
> sn: Nova
> Expected behavior is LDAP Error code: 20 (Indicates that the attribute value specified in a modify or add operation already exists as a value for that attribute). This is quite similar to DIREVE-241 ("Adding an already existing attribute value with a modify operation does not cause an error."). But in this case, the attribute value is not present before, but is created with a single modify operation with two add changes. OK, it is a little bit bizarre, but other LDAP servers successfully refuse such an operation.
> Find attached a test case with two tests, one for an already existing attribute type, and one for a new type (the issue arises in both occasions).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira