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

Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2020/05/04 18:04:00 UTC

[jira] [Resolved] (SLING-9422) Content Package Installer: Use service resource resolvers instead of admin resource resolver for installation

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

Konrad Windszus resolved SLING-9422.
------------------------------------
    Resolution: Fixed

Fixed in https://github.com/apache/sling-org-apache-sling-installer-factory-packages/commit/8c14843c254476964ad62795a2d2b67bce6a3a5e.

> Content Package Installer: Use service resource resolvers instead of admin resource resolver for installation
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: SLING-9422
>                 URL: https://issues.apache.org/jira/browse/SLING-9422
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Installer Packages Factory 1.0.4
>
>
> Currently the {{PackageTransformer}} uses an an administrative session. Instead {{SlingRepository.loginService()}} should be used together with an according service user mapping. The user needs basically write access to all locations which is covered by packages and {{/etc/packages}} itself.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)