[
https://issues.apache.org/jira/browse/SLING-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14319942#comment-14319942
]
Felix Meschberger commented on SLING-3854:
------------------------------------------
[~asanso] Patch LGTM with a nitpick: It raises the Jackrabbit API dependency
rather high. Can we live with that ? Do we do that with open eyes ? Then I am
fine. Otherwise, we might discuss how to cope with older Jackrabbit API which
does not have the User.isSystemUser method.
Validation: I think a user cannot easily dynamically convert its status of
being a regular or a system user. Hence it is probably stable enough to
validate at configuration time and not on each access.
> 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
> Assignee: Antonio Sanso
> Attachments: SLING-3854-patch2.txt, 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)
