[MGNLUI-2588] Editing ACLs in Roles doesn't work properly Created: 13/Jan/14  Updated: 23/Jan/14  Resolved: 22/Jan/14

Status: Closed
Project: Magnolia UI
Component/s: security app
Affects Version/s: 5.2.1
Fix Version/s: 5.2.2

Type: Bug Priority: Blocker
Reporter: Maja Assignee: Jaroslav Simak
Resolution: Fixed Votes: 1
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLDAM-367 Editing ACLs in Roles doesn't work pr... Closed
duplicate
is duplicated by MGNLDAM-367 Editing ACLs in Roles doesn't work pr... Closed
is duplicated by MGNLUI-2539 Cannot delete ACL for a Role Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When editing roles in Security configuration - Access Control List tab, user cannot delete acls in category, contacts, dam, data,... For example: When deleting one acl it seems like the acl has been deleted correctly,but after saving and reopening current role, the deleted acl can still be seen on the list.
Workaround is to export role and manually delete acls.



 Comments   
Comment by Jan Haderka [ 13/Jan/14 ]

confirmed as superuser on demoauthor

Comment by Jaroslav Simak [ 22/Jan/14 ]

About the fix:
When we create a role via role manager, we automatically add a node with read only permissions for the role itself. This caused some errors when acl nodes were re-added to the role node.

Generated at Mon Feb 12 08:58:10 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.