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

Posted to dev@sling.apache.org by "angela (JIRA)" <ji...@apache.org> on 2017/06/22 16:55:00 UTC

[jira] [Updated] (SLING-6981) Adjust ResourceResolverFactoryImpl and CommonsResourceResolverFactoryImpl to reflect SLING-6963

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

angela updated SLING-6981:
--------------------------
    Summary: Adjust ResourceResolverFactoryImpl and CommonsResourceResolverFactoryImpl to reflect SLING-6963  (was: Adjust ResourceResolverFactoryImpl to reflect SLING-6963)

> Adjust ResourceResolverFactoryImpl and CommonsResourceResolverFactoryImpl to reflect SLING-6963
> -----------------------------------------------------------------------------------------------
>
>                 Key: SLING-6981
>                 URL: https://issues.apache.org/jira/browse/SLING-6981
>             Project: Sling
>          Issue Type: Improvement
>          Components: ResourceResolver
>            Reporter: angela
>         Attachments: SLING-6981.patch
>
>
> While testing the proposed extension to the service-user-mapping in a real world scenario, I noticed that also the {{ResourceResolverFactoryImpl#getServiceResourceResolver}} makes used of the {{ServiceUserMapper}} and needs to be adjusted to reflect the fact that it can be either a service-user-name or a set of service-principal-names.
> I can attach an initial patch for this but I have to admit that I am less familiar with that part of Sling (compared to the service user mapper and the jcr-component). So, I might have missed relevant parts or other areas around the resource resolver that make use of the mapping.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)