You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Angela Schreiber (Jira)" <ji...@apache.org> on 2021/04/09 11:47:00 UTC
[jira] [Created] (SLING-10286) Converter ignores disabled status of
system user
Angela Schreiber created SLING-10286:
----------------------------------------
Summary: Converter ignores disabled status of system user
Key: SLING-10286
URL: https://issues.apache.org/jira/browse/SLING-10286
Project: Sling
Issue Type: Bug
Components: Content-Package to Feature Model Converter
Affects Versions: Content-Package to Feature Model Converter 1.0.24
Reporter: Angela Schreiber
[~kpauls], IMHO the content-package-2-fm-converter should spot if system-users are marked as disabled (i.e. if they have {{rep:disabled}} property set and should reflect that in the set of repo-init statements generated upon conversion.
While this is probably not a very common scenario it still has a significant impact as disabled system users are not allowed in sling service user mappings (and should allowed to login).
the fix should be straight forward:
- test if rep:disabled exists with users/system-users
- extend User/SystemUser to allow to have a 'disable-reason' set (groups can't be disabled)
- when generating repo-init statements in {{DefaultAclManager}} add an additional {{DisableServiceUser}} operation if a user is marked as disabled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)