![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
5.x |
|
Assignee:
|
Tobias Mattsson
|
|
Attachments:
|
ACLs_for_deptOne-admin.png |
|
Created:
|
06/Nov/13 3:54 PM
|
|
Description:
|
After enabling the role "deptOne-admin" to access the securityApp by adding it to
/modules/security-app/apps/security/permissions/roles
I get different behavior when editing a group or a role within a folder structure "deptOne-admin" has permissions for (this is a multi-tenancy use case).
As user having the "deptOne-admin" role I'm able to select and edit a group within "my" "/departmentOne" folder but when selecting "Edit role" in "Roles" an exception is thrown:
info.magnolia.ui.api.action.ActionExecutionException: javax.jcr.PathNotFoundException: /modules/security-app/dialogs/role
After adding the ACL
Config - Read Only - Selected and sub node - /modules/security-app/dialogs/role
to the "deptOne-admin" role, everything works fine.
The behavior for groups and roles should be consistent and in an ideal way it would be enough to just add the "deptOne-admin" role to the list of allowed roles within the securityApp.
|
|
Fix Versions:
|
5.x |
|
Project:
|
Magnolia UI
|
|
Priority:
|
![Neutral]() Neutral
|
|
Reporter:
|
Lars Fischer
|
|
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]>
----------------------------------------------------------------
