[
https://issues.apache.org/jira/browse/DIRSTUDIO-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006868#comment-13006868
]
Kiran Ayyagari commented on DIRSTUDIO-729:
------------------------------------------
It is perfectly valid when performed by an admin user. I think the
OperationalAttributeInterceptor is behaving odd in the case of entryCSN which
needs to be checked. Having said that, we do need to add few more checks to
prevent addition of duplicate entryUUID and entryCSN values (some presence
checks on the corresponding indexes in the Partition's add operation will
prevent this from happening)
> Issue when creating an entry copying an existing one
> ----------------------------------------------------
>
> Key: DIRSTUDIO-729
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-729
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-ldapbrowser
> Affects Versions: 1.5.3
> Reporter: Emmanuel Lecharny
> Fix For: 2.0.0
>
>
> When creating a new entry, copying it from an existing entry, we get an error
> :
> [LDAP: error code 19 - entryCSN : no user modification allowed]
> The connection has been set to require the OperationalAttributes to be read
> when fetching entries. I'm wondering if the problem is not a side effect :
> the copied entry gets all its OpAttrs copied too, when they should not.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
