Carsten Ziegeler created SLING-7930:
---------------------------------------
Summary: Provide default ServiceUserMapped services
Key: SLING-7930
URL: https://issues.apache.org/jira/browse/SLING-7930
Project: Sling
Issue Type: Improvement
Components: Service User Mapper
Reporter: Carsten Ziegeler
One goal of Sling is to be configurationless. With SLING-6772, the service user
mapper module introduces a default for service user mappings. However this does
not include registering a ServiceUserMapped service - but, other services in
the system have a reference on such services to ensure that a mapping is
available.
In addition, currently ServiceUserMapped only ensures that a "mapping" is
available, but not the service user itself
This has been recently discussed in the Sling mailing list
[https://lists.apache.org/thread.html/b7a00588cd6c44078d38572b38002965916c9f18dedd9a64380428ad@%3Cdev.sling.apache.org%3E]
We would use the existing service hooks to see if for any given
ServiceUserMapped requested we can actually log into all registered resource
providers that require authentication and are not lazy. If a login exception
occurs, it's not available and we don't register the ServiceUserMapped.
Obviously, if a resource provider gets added that requires authentication and
is not lazy we need to recheck but this way we at least would neither exposes
service users to the world nor, require API changes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
