![]() |
|
|
|
|
Issue Type:
|
Bug
|
|
Affects Versions:
|
5.2.6 |
|
Assignee:
|
Unassigned |
|
Components:
|
security app |
|
Created:
|
18/Jun/14 9:34 AM
|
|
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. ![]()
|
|
Project:
|
Magnolia UI
|
|
Priority:
|
Major
|
|
Reporter:
|
Marvin Kerkhoff
|
|
Security Level:
|
Public |
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------