[
https://issues.apache.org/jira/browse/SLING-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated SLING-6981:
--------------------------
Attachment: SLING-6981.patch
proposed patch for {{ResourceResolverFactoryImpl.getServiceResolver}}. I was
looking for some test coverage of that method to make sure I can provide test
for the variant with principal-names mapping... but couldn't find any tests for
that. Missing something?
> Adjust ResourceResolverFactoryImpl 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)
