[
https://issues.apache.org/jira/browse/OAK-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052247#comment-14052247
]
angela commented on OAK-1943:
-----------------------------
the flow is as follows:
- the user node gets created
- the protected password property is handled by UserImporter and triggers the
creation of the rep:pwd node
- further processing the ImportImpl detects that protected the rep:pwd node
already exists and ignores it along with it's properties.
IMO we have the following possibilities:
1. we adjust the ImporterImpl such that protected child properties of that
existing protected node trigger a call to the protectedpropertyimporters. this
would be required if we think that the rep:pwd node may contain additional
information that must be importer or if we think that the
rep:passwordLastModified should not be generated but taken over from the
imported content (i would rather not do the latter)
2. we leave the ImporterImpl as is if we assume that everything underneath
rep:pwd is (or must be) auto-created by the user management implementation and
should never be imported -> change the test cases to reflect this.
[~djaeggi], what do you think?
> UserImporter doesn't import protected rep:passwordLastModified
> --------------------------------------------------------------
>
> Key: OAK-1943
> URL: https://issues.apache.org/jira/browse/OAK-1943
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 1.1
> Reporter: angela
> Fix For: 1.1
>
>
> while writing a dedicated test case for user import along with OAK-1922
> [~djaeggi] found that the rep:passwordLastModified is not being imported.
> in order not to block the initial feature request, we decided to move that in
> a separate issue and ignore the corresponding test with an corresponding link
> to this issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
