You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2019/07/30 12:01:00 UTC

[jira] [Created] (OAK-8518) PrincipalPolicyImporter: handle rep:effectivePath property generated by xml-export for repository level

angela created OAK-8518:
---------------------------

             Summary: PrincipalPolicyImporter: handle rep:effectivePath property generated by xml-export for repository level
                 Key: OAK-8518
                 URL: https://issues.apache.org/jira/browse/OAK-8518
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: authorization-principalbased
    Affects Versions: 1.18.0
            Reporter: angela
            Assignee: angela


the property storing the {{rep:effectivePath}} is defined to be of type PATH. due to the fact that {{NamePathMapperImpl#getJcrName(String)}} converts an empty oak path to the current path element ("."), any XML roundtrip (i.e. xml-export followed by xml-import) will fail to properly handle principal-entries for the repository level (i.e. null path that gets stored as empty string).

The fix should be straight forward by adjusting the {{PrincipalPolicyImporter}} such that reading the {{rep:effectivePath}} propInfo (or the {{rep:nodePath}} restriction) adjust the string value accordingly.

[~stillalex], fyi




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)