[
https://issues.apache.org/jira/browse/SLING-9975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved SLING-9975.
-------------------------------
Resolution: Fixed
> RepPolicyEntryHandler ignores restrictions defined in jackrabbit2 format
> ------------------------------------------------------------------------
>
> Key: SLING-9975
> URL: https://issues.apache.org/jira/browse/SLING-9975
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Reporter: Angela Schreiber
> Assignee: Angela Schreiber
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.0.26
>
>
> {{RepPolicyEntryHandler}} will read restrictions only from the
> {{rep:restrictions}} child node (primarytype {{rep:Restrictions}}):
> https://github.com/apache/sling-org-apache-sling-feature-cpconverter/blob/ffc6bb990dfaf82c477a28ad4b87b0c12859b743/src/main/java/org/apache/sling/feature/cpconverter/handlers/RepPolicyEntryHandler.java#L179-L188
> according to the documentation in Jackrabbit Oak the old jackrabbit2-variant
> of defining restrictions is still supported from the node type definition of
> an access control entry:
> http://jackrabbit.apache.org/oak/docs/security/authorization/restriction.html#representation
> this should be reflected in the handler in order not to generate repo-init
> statements that unintentionally create a different access control setup and
> ultimately alter the effective permissions present in the given repository.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
