[MGNLUI-3011] Bad access rights inside module app configuration Created: 18/Jun/14  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: security app
Affects Version/s: 5.2.6
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Marvin Kerkhoff Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

Hi there,

i found out that there are some realy bad access rights inside some configuration of modules. For Example look at /modules/pages/apps/pages/subApps/browser/actions/activateDeletion/availability/access/roles

There you see one role "demo-project-publisher" sometimes also "demo-project-editor" is used. I guess it is very tricky and i don't get the usecase for those access rights. In my case i had no clue why this function doesn't work because i only searched for reasons in the security app. With those access rights inside existing modules it is far away from a userfriendly security system. It is to complicated and the access rights are scattered all around the JCR.



 Comments   
Comment by Roman Kovařík [ 09/Mar/21 ]

https://demo.magnolia-cms.com/.magnolia/admincentral#app:configuration:browser;/modules/pages/apps/pages/subApps/browser/actions/activateDeletion/availability:treeview:

Generated at Mon Feb 12 09:02:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.