Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Wed, 13 Aug 2014 11:05:12 +0000 (UTC)
From: "angela (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12732778.1407484213407.70969.1407927912175@arcas>
In-Reply-To: <JIRA.12732778.1407484213407@arcas>
References: <JIRA.12732778.1407484213407@arcas>
Subject: [jira] [Updated] (JCR-3802) User Management: API for System Users
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

angela updated JCR-3802:
------------------------

    Attachment: JCR-3802__adjusting_filevault.patch

[~tripod], i thing you would need to adjust the filevault project... attached a first draft with some TODOs... in particular for the ServiceProviderFactory which doesn't allow to use another version than Jr2.x

> 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
>         Attachments: JCR-3802___POC_implementation_for_Oak.patch, JCR-3802___POC_implementation_for_Oak_2.patch, JCR-3802__adjusting_filevault.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.2#6252)