Details
-
Improvement
-
Status: Resolved
-
Critical
-
Resolution: Won't Do
-
None
-
None
-
None
Description
For content distribution we use a user mapping with a subservice like:
"org.apache.sling.distribution.journal:importer=[sling-distribution-importer,sling-distribution,content-writer-service,repository-reader-service,version-manager-service,group-administration-service,user-administration-service,namespace-mgmt-service]"
Angela explained to me that if any of the subjects in the list is not principal based then the whole subservice will fall back to default authoristation. This can lead to unexpected access denied issues that are difficult to debug.
So it would be great if we could add some warn logging that cleary tells us that our subservice is possibly not working as expected.
Attachments
Issue Links
- links to