[
https://issues.apache.org/jira/browse/SLING-4461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358707#comment-14358707
]
Marius Petria commented on SLING-4461:
--------------------------------------
One more thought. To some extent the ServiceUserMapped interface offers a
solution to the non-determinism introduced by defaults. More exactly, one can
avoid the defaults by configuring a ServiceUserMapped reference with a specific
subService target. It is not very clean but it makes the defaults avoidable
without introducing a breaking change like removing them completely.
[~fmeschbe], [~cziegeler], what is your preference? Should we keep the
fallbacks? Is this blocking the release of SLING-4312?
> Remove fallbacks for service users resolution
> ---------------------------------------------
>
> Key: SLING-4461
> URL: https://issues.apache.org/jira/browse/SLING-4461
> Project: Sling
> Issue Type: Improvement
> Components: Service User Mapper
> Reporter: Marius Petria
> Fix For: Service User Mapper 1.1.2
>
>
> ServiceUserMapperImpl has several levels of fallback for service user
> resolution (fallback to bundle default, or to global default). While this
> offers a lot of flexibility, it introduces non-determinism in a security
> feature. If defaults are set, it can happen (especially at startup) that code
> is executed using different serviceUsers, e.g. a component can execute using
> the bundle default or global default until its specific subService is
> available, and it can be easily imagined how this can cause subtle errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
