[
https://issues.apache.org/jira/browse/SLING-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated SLING-3854:
--------------------------
Attachment: SLING-3854.patch
untested patch proposing a validating interface; also service implementing the
validator based on a jcr repository.
note: the patch also changes the log level to error if an invalid mapping is
passed (which should IMO never happen and should be reported as error) and
removes a superfluous colon ;-).
note 2: i find the term 'userName' a bit confusing when all the related methods
then call it userID.
> Add configuration option to restrict service user mapper to system users
> ------------------------------------------------------------------------
>
> Key: SLING-3854
> URL: https://issues.apache.org/jira/browse/SLING-3854
> Project: Sling
> Issue Type: Improvement
> Components: Service User Mapper
> Reporter: angela
> Attachments: SLING-3854.patch
>
>
> JCR-3802 introduces the concept of system users that distinct from regular
> user accounts and never have a password set. the API extensions include to
> following ability to discover if a given User is actually a system user:
> {{User.isSystemUser}}.
> It would be good if the service user mapping had a configuration option that
> would restrict the mapping to dedicated service users i.e. to users which are
> defined to be system users in case sling is running on a JCR repository that
> implements jackrabbit API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
