[jira] [Resolved] (SLING-9735) Remove loginAdministrative() usage from org.apache.sling.jcr.contentloader

["Eric Norman (Jira)" <ji...@apache.org>]

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

Eric Norman resolved SLING-9735.
--------------------------------
    Resolution: Fixed

Fixed at: [https://github.com/apache/sling-org-apache-sling-jcr-contentloader/commit/2647cbf573790e756a7f31793bcb680d79606483]

 

NOTE: after upgrade to version 2.4.0 or later the following additional configurations must be added to your system and the contentloader bundle should be removed from the "org.apache.sling.jcr.base.internal.LoginAdminWhitelist.fragment-sling" configuration.
{code:java}
[:repoinit]

    # jcr bundle contentloader
    create service user sling-content-loader

    set ACL for sling-content-loader 
        allow   jcr:all    on / 
    end

[configurations]  org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-jcr-contentloader
    user.mapping=[
      "org.apache.sling.jcr.contentloader\=sling-content-loader"
    ]{code}
 

 

> 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)