Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
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.
Attachments
Attachments
Issue Links
- blocks
-
JCRVLT-56 Add support for oak system users
- Closed
- is related to
-
OAK-7952 JCR System users do no longer consider group ACEs of groups they are member of
- Resolved
- relates to
-
SLING-3854 Add configuration option to restrict service user mapper to system users
- Closed
-
OAK-2034 Update parent pom.xml to latest 2.9 release
- Closed