Apache Directory Project - [jira] Updated: (DIREVE-268) Adding a duplicate attribute value should cause an error.

This is Interesting: Free IT Magazines  
Home > Archive > Apache Directory Project > September 2005 > [jira] Updated: (DIREVE-268) Adding a duplicate attribute value should cause an error.





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author [jira] Updated: (DIREVE-268) Adding a duplicate attribute value should cause an error.
Stefan Zoerner (JIRA)

2005-09-25, 5:45 pm

[ http://issues.apache.org/jira/brows...VE-268?page=all ]

Stefan Zoerner updated DIREVE-268:
----------------------------------

Attachment: ModifyAddDuplicateValueTest.java

Here is the test case for the described issue.

> 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
> 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 mo

dify 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/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com