[
https://issues.apache.org/jira/browse/DIRSTUDIO-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006898#comment-13006898
]
Stefan Seelmann commented on DIRSTUDIO-729:
-------------------------------------------
Operational attributes - to be more precise attributes with the
NO_USER_MODIFICATION flag - are filtered when copying an entry or when using an
existing entry as template in the 'new entry' wizard.
If I understand Emmanuel right only the entryCSN attribute is affected. I was
able to reproduce this with OpenLDAP. The problem is that entryCSN isn't
included in OpenLDAP's schema, there is an open bug at the OpenLDAP issue
tracker: http://www.openldap.org/its/index.cgi/Development?id=5573.
So there is no change to find out that entryCSN isn't writeable. We can
hard-code that attribute or add a configuration dialog to configure
non-writeable attributes.
> 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
