[jira] [Commented] (JCR-3802) User Management: API for System Users

["Julian Reschke (JIRA)" <ji...@apache.org>]

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

Julian Reschke commented on JCR-3802:
-------------------------------------

trunk: [r1618123|http://svn.apache.org/r1618123] [r1618122|http://svn.apache.org/r1618122]


> User Management: API for System Users
> -------------------------------------
>
>                 Key: JCR-3802
>                 URL: https://issues.apache.org/jira/browse/JCR-3802
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-api
>            Reporter: angela
>            Assignee: angela
>             Fix For: 2.9
>
>         Attachments: JCR-3802__adjusting_filevault.patch, JCR-3802___POC_implementation_for_Oak_2.patch, JCR-3802___POC_implementation_for_Oak.patch, JCR-3802_proposed_API.patch
>
>
> Apache Sling recently added the ability to define dedicated service users that allows to replace the troublesome {{SlingRepository.loginAdministrative}} with {{SlingRepository.loginService}}.
> In a default Sling repository backed by a Jackrabbit/Oak content repository this results in user accounts being created for these service users.
> Since these service users are never expected to represent a real subject that has a userId/password pair or profile information editable by this very subject, I figured out that it may be useful to cover these service users with the following API extensions, which would allow us to identify if a given user account is in fact a service (or system) user. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)