[
https://issues.apache.org/jira/browse/JCRVLT-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840721#comment-17840721
]
Timothee Maret commented on JCRVLT-751:
---------------------------------------
This appears to be related to how the resource hierarchy is serialised in the
package.
When the node is serialised as a folder (like in the failing test) the test
fails.
When the node is serialised inside a .content.xml document, the test succeeds
(mounting at the / triggers this behaviour, see
[here|https://github.com/apache/jackrabbit-filevault/pull/335/commits/6e8169916e7479dbe440fab239f898ac4d2967fe]).
> Can't import a user with parent folder that starts with _ and includes
> another _
> ---------------------------------------------------------------------------------
>
> Key: JCRVLT-751
> URL: https://issues.apache.org/jira/browse/JCRVLT-751
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: vlt
> Affects Versions: 3.7.2
> Reporter: Timothée Maret
> Priority: Major
> Labels: vault
>
> AEM has a user synchronisation capability in the publish tier. The
> synchronisation mechanism relies on FileVault to export and import content.
> Users stored in the repository under a path that starts with a _ and that
> contain another _ can be exported but fail to be re-imported. For instance,
> the user stored under the path /home/users/test/_6k_test-user-a won't be
> imported.
> Debugging this issue, it seems that FileVault treats the _6k_ pattern as a
> namespace and thus skip the resource upon import because the paths don't
> match.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
