You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2014/08/08 09:52:11 UTC

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

angela created JCR-3802:
---------------------------

             Summary: 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: JCR API
            Reporter: angela


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)