You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Marius Petria (JIRA)" <ji...@apache.org> on 2015/02/27 13:56:04 UTC

[jira] [Created] (SLING-4461) Remove fallbacks for service users resolution

Marius Petria created SLING-4461:
------------------------------------

             Summary: 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


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)