[MAGNOLIA-5531] Logically inconsistent ACLs - behaviour and user feedback Created: 09/Dec/13  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia
Component/s: security
Affects Version/s: 5.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Rainer Blumenthal Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux


Attachments: JPEG File screenshot-1.jpg     JPEG File screenshot-2.jpg    
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   

If you enter accidentally a logically inconsistent ACL setting,

  • the dialog won't save anymore:
Error: An error occurred while executing an action.[MORE]
  • adding other ACL fields is no longer possible:
Error: Invocation of method buttonClick in info.magnolia.security.app.dialog.field.WorkspaceAccessFieldFactory$1 failed.
[MORE]
  • the message I get in the pulse is completely useless
  • in one constellation the role was even empty after saving the dialog (but not reproducable - and very risky )

See screenshots. I hope the issue is correct in the Core.



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 04:06:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.