jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (JCR-3802) User Management: API for System Users
Date Wed, 13 Aug 2014 11:29:11 GMT

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

angela edited comment on JCR-3802 at 8/13/14 11:27 AM:
-------------------------------------------------------

well... sure... you can do that... but i don't plan to implement the same thing in Jackrabbit
2.x unless we have a compelling reason why this is needed... then there is the CUG prototype
in Oak which introduces a new type of access control policy and which for sure will not be
backported to Jackrabbit 2.x. After all i don't care too much but it looked just wrong to
me to add it to Jackrabbit 2.x if in fact it's Oak... and there might be other things in Oak
that need special treatment (thinking e.g. of the privilege definitions now stored in the
repository)


was (Author: anchela):
well... sure... you can do that... but i don't plan to implement the same thing in Jackrabbit
2.x unless we have a compelling reason why this is needed... then there is the CUG prototype
in Oak which introduces a new type of access control policy and which for sure will not be
backported to Jackrabbit 2.x. After all i don't care to much but it looked just wrong to me
to add it to Jackrabbit 2.x if in fact it's Oak... and there might be other things in Oak
that need special treatment (thinking e.g. of the privilege definitions now stored in the
repository)

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

Mime
View raw message