[
https://issues.apache.org/jira/browse/SLING-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681819#comment-14681819
]
Konrad Windszus commented on SLING-3854:
----------------------------------------
I don't see the configuration option to disable that functionality. Was that
deliberately left out? If I intentionally want to use regular users as service
users I now have to implement my own {{ServiceUserValidator}} which returns
{{true}} for {{isValid(...)}}. Wouldn't a simple OSGi flag on the service user
mapper be better to not enforce that check?
> 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
> Fix For: Service User Mapper 1.1.0, JCR Resource 2.5.0
>
> 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)
