[MAGNOLIA-4989] Permissions for operations Created: 24/Apr/13  Updated: 15/May/13  Resolved: 15/May/13

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: 4.5.9

Type: New Feature Priority: Neutral
Reporter: Roman Kovařík Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-4476 Add functionality to disable delete o... Closed
is depended upon by MGNLUI-1345 Change action and actionbar section r... Closed
is depended upon by MGNLUI-1038 Add functionality to disable delete o... Closed
is depended upon by MAGNOLIA-5010 Add functionality to disable delete o... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Implement OperationPermissionDefinition:

getRead()
getDelete()
getWrite()
getExecute()
getAdd()...for example for areas
getModify()
...
canMove(User user)
...

Place the definitions to new package info.magnolia.cms.security.operations



 Comments   
Comment by Tobias Mattsson [ 13/May/13 ]

Some changes necessary to make the definition classes usable for configuration in UI:

  • Rename RolesDefinition to AccessDefinition
  • Move evaluation logic in ConfiguredOperationPermissionDefinition to AccessDefinition
    • Existing evaluation logic should delegate
Generated at Mon Feb 12 04:00:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.