-
Bug
-
Resolution: Fixed
-
Major
-
5.2.10, 5.3.5
-
None
-
-
Empty show more show less
-
Sprint 3 (Basel)
-
1
Deleting folders of groups or roles (security app) will always check for users having assigned a group OR a role with the name of the items in that folder. This might result in cases where one cannot delete a folder containing a group "foo" because there's also a role "foo" which is assigned to a user. Deleting a folder of groups should only check for users and groups having that group assigned (and not for those having assigned a role with that name) - likewise deleting a folder of roles should only check for users and groups having that role assigned (and not for those having assigned a group with that name).
to reproduce:
- open security app
- go to groups
- create a folder "untitled"
- create a group "group-or-role-name" within the above folder
- go to roles
- create a role "group-or-role-name" (doesn't matter whether this is on root or in a folder)
- go to users, select one (e.g. peter) and assign him the ROLE "group-or-role-name"
- go to groups, select the folder "untitled" and try to delete it
-> system will tell you, you cannot remove that folder because user peter users "group-or-role-name" but actually it only uses the so called role not the group and hence the deletion should be allowed!
Note: also the provided error message should be improved (filed as MGNLUI-3093)
- caused by
-
MGNLUI-3062 Deleting not empty folders in groups and roles does not work
- Closed
- is related to
-
MGNLUI-3276 Deleting groups or roles is too slow if there's a lot of users in jcr
- Closed
- relates to
-
MGNLUI-3258 When deleting groups/roles dependencies have to be removed manually
- Closed