directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Ayyagari (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DIRSERVER-1449) EntryUUID AT should not be accepted for a Add, Delete or Modify operation
Date Wed, 26 May 2010 20:33:41 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kiran Ayyagari resolved DIRSERVER-1449.
---------------------------------------

    Resolution: Fixed

Updated the exception thrown from OperationAttributeInterceptor during add operation.
The schemainterceptor handles the same checks during modify operation so no additional checks
were placed in OP AT interceptor's
modify operation.

Added test cases to confirm the behavior

http://svn.apache.org/viewvc?rev=948572&view=rev

> EntryUUID AT should not be accepted for a Add, Delete or Modify operation
> -------------------------------------------------------------------------
>
>                 Key: DIRSERVER-1449
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1449
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-RC1
>            Reporter: Emmanuel Lecharny
>            Assignee: Kiran Ayyagari
>            Priority: Critical
>             Fix For: 2.0.0-RC1
>
>
> Right now, the OperationalAttributeInterceptor simply replace the entryUUID value with
another one, when we submit a Add operation with such an entryUUID in the entry. 
> This is wrong. We should simply reject the operation as the entryUUID is NO-USER-MODIFICATION.
> However, we should keep in mind that Syncrepl will inject entries with such elements,
so it all depend on the session used to inject data.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message