[
https://issues.apache.org/jira/browse/JCRVLT-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840140#comment-17840140
]
Konrad Windszus edited comment on JCRVLT-751 at 4/23/24 3:31 PM:
-----------------------------------------------------------------
In my tests the node path {{/home/users/test/_6k_test-user-a}} is exported as
ZIP path {{/home/users/test/__6k_test-user-a}} (which is correct according to
https://jackrabbit.apache.org/filevault/vaultfs.html#filename-escaping) and
correctly unescaped to node path {{/home/users/test/_6k_test-user-a}} during
import.
was (Author: kwin):
In my tests the node path `/home/users/test/_6k_test-user-a` is exported as ZIP
path `/home/users/test/__6k_test-user-a` (which is correct according to
https://jackrabbit.apache.org/filevault/vaultfs.html#filename-escaping) and
correctly unescaped to node path `/home/users/test/_6k_test-user-a` during
import.
> 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)
