[ 
https://issues.apache.org/jira/browse/SLING-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14328780#comment-14328780
 ] 

Marius Petria edited comment on SLING-3854 at 2/20/15 10:30 AM:
----------------------------------------------------------------

Hi [~asanso], is there any reason for which the validation is done at mapping 
time not at registration time? That could potentially introduce some 
performance problems especially if the validator is hitting the repository.

EDIT: Also, regarding switching to a service user in JcrSystemUserValidator 
this will not be very easy probably as it looks like it will cause an infinite 
loop.


was (Author: mpetria):
Hi [~asanso], is there any reason for which the validation is done at mapping 
time not at registration time? That could potentially introduce some 
performance problems especially if the validator is hitting the repository.

> 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)

Reply via email to