[
https://issues.apache.org/jira/browse/SLING-9735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199601#comment-17199601
]
Eric Norman edited comment on SLING-9735 at 9/21/20, 7:09 PM:
--------------------------------------------------------------
[~rombert] I'm not aware of any scenarios where the jcr.contentloader would be
modifying namespaces or node types. Do you know of a use case where that would
come into play? If you are referring to the handling of the "Sling-Nodetypes"
and "Sling-Namespaces" bundle headers, then those are handled by a the jcr.base
bundle.
In any case, specific deployments should be free to map the service user to
whatever is most appropriate, so the sling-package-install would probably
satisfy the general use requirements since it has the expected privileges.
was (Author: enorman):
[~rombert] I'm not aware of any scenarios where the jcr.contentloader would be
modifying namespaces or node types. Do you know of a use case where that would
come into play? If you are referring to the handling of the "Sling-Nodetypes"
and"Sling-Namespaces" bundle headers, then those are handled by a the jcr.base
bundle.
In any case, specific deployments should be free to map the service user to
whatever is most appropriate, so the sling-package-install would probably
satisfy the general use requirements since it has the expected privileges.
> Remove loginAdministrative() usage from org.apache.sling.jcr.contentloader
> --------------------------------------------------------------------------
>
> Key: SLING-9735
> URL: https://issues.apache.org/jira/browse/SLING-9735
> Project: Sling
> Issue Type: Improvement
> Reporter: Eric Norman
> Assignee: Eric Norman
> Priority: Major
> Fix For: JCR ContentLoader 2.4.0
>
>
> Create a service user and replace usage of loginAdministrative() to use that
> service user.
>
> Counted 4 occurrences in the current source code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
