[
https://issues.apache.org/jira/browse/DIRSTUDIO-729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006904#comment-13006904
]
Emmanuel Lecharny commented on DIRSTUDIO-729:
---------------------------------------------
Thanks Stefan for the heads-up.
I wrote a mail about the EntryCSN and EntryUUID OpAttrs a while back :
http://web.archiveorange.com/archive/v/DCLZ8UmAvYgfzVPFCyD8
EntryCSN is supposed to have the NO_USER_MODIFCATION flag.
It is declared this way in OpenLDAP (in servers/slapd/schema_prep.c):
{ "entryCSN", "( 1.3.6.1.4.1.4203.666.1.7 NAME 'entryCSN' "
"DESC 'change sequence number of the entry content' "
"EQUALITY CSNMatch "
"ORDERING CSNOrderingMatch "
"SYNTAX 1.3.6.1.4.1.4203.666.11.2.1{64} "
"SINGLE-VALUE NO-USER-MODIFICATION USAGE
directoryOperation )",
NULL, SLAP_AT_HIDE,
NULL, NULL,
NULL, NULL, NULL, NULL, NULL,
offsetof(struct slap_internal_schema, si_ad_entryCSN) },
(OpenLDAP 2.4.24)
> 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
