[SLING-6981] Adjust ResourceResolverFactoryImpl and CommonsResourceResolverFactoryImpl to reflect SLING-6963

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Resource Resolver 1.5.28
• Component/s: ResourceResolver
• Assignee: Karl Pauls
• Reporter: Angela Schreiber
• Created: 22/Jun/17 15:22
• Updated: 21/Jul/17 12:36
• Resolved: 10/Jul/17 15:50

Description

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.

Issue Links

• depends upon: SLING-6963 Service user declaration based on principal names