-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
-
Empty show more show less
-
Empty show more show less
-
Yes
-
Beta 2, Beta 3
Outlined in http://wiki.magnolia-cms.com/display/DEV/Concept+-+Action+availability+and+access+control
- Change the term restrictions to availability for actions
- Move roles configuration to a sub node permissions and use the existing class from core for it
- Node types stays where it is
- Change the term restrictions to availability as well for actionbar
- Should use the same configuration object as for actions
- This means we'll also have permissions on sections and we should evaluate these as well
- Definitions should have evaluation logic in themselves to allow for custom classes with custom evaluation logic
The existing classes mentioned were introduced in MAGNOLIA-4989
- depends upon
-
MAGNOLIA-4989 Permissions for operations
- Closed
- is causing
-
MGNLUI-1380 Write test for BrowserSubApp.updateActionbar method
- Closed
- is depended upon by
-
MGNLDAM-216 AssetsMainSubApp should control appearance of the actionbar using configuration
- Closed
-
MGNLUI-1244 Config, Pages and Security apps should use configuration to control actionbar appearence
- Closed
- is related to
-
MGNLDAM-222 Introduce Restrictions for action definition
- Closed
-
MGNLUI-1377 Workbench: root path not respected, creating a user fails in security
- Closed
-
MGNLUI-1603 Implement rule based column availability like for actions
- Closed