You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/04/30 14:09:00 UTC

[jira] [Updated] (JCRVLT-751) ExportOptions.rootPath not properly unescaped during filter rule mapping

     [ https://issues.apache.org/jira/browse/JCRVLT-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus updated JCRVLT-751:
-----------------------------------
    Summary: ExportOptions.rootPath not properly unescaped during filter rule mapping  (was: Can't import a user with parent folder that starts with _ and includes another _ )

> ExportOptions.rootPath not properly unescaped during filter rule mapping
> ------------------------------------------------------------------------
>
>                 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)