[JCR-3802] User Management: API for System Users

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9
• Component/s: jackrabbit-api
• Assignee: Angela Schreiber
• Reporter: Angela Schreiber
• Created: 08/Aug/14 07:50
• Updated: 10/Dec/18 12:47
• Resolved: 15/Aug/14 09:34

Description

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.

Issue Links

• blocks: JCRVLT-56 Add support for oak system users
• is related to: OAK-7952 JCR System users do no longer consider group ACEs of groups they are member of
• relates to: SLING-3854 Add configuration option to restrict service user mapper to system users
• relates to: OAK-2034 Update parent pom.xml to latest 2.9 release