Menu/authorization: need alternative to rails controller centric authorization
The methods authorized? and allowed_to should be less controller centric.
In bastion we only have one controller: https://github.com/Katello/katello/blob/master/engines/bastion/app/controllers/bastion/bastion_controller.rb. That controller simply renders html, js, and css which in turn powers the application.
We cannot show menu items based on permissions because the menu item authorization relies on there being a controller `entity` with an action `action`. We need some way to specify the entity and action without undue reliance on the existence of a rails controller.
One solution ehelms proposed was to "allow passing in a Proc to define a path or pass in 'url' if the user wants to".
#1 Updated by Walden Raines almost 9 years ago
- Blocks Feature #5217: As a user, I should have CRUD permissions for all entities that are exposed to me. added
#2 Updated by Anonymous almost 9 years ago
- Assignee set to Anonymous
- Status changed from New to Ready For Testing
#3 Updated by Dominic Cleal almost 9 years ago
- Target version set to 1.8.3
#4 Updated by Walden Raines almost 9 years ago
- Blocks Feature #5593: Fix menu so authorized items are displayed post single page app work added
#5 Updated by Dominic Cleal almost 9 years ago
- Legacy Backlogs Release (now unused) set to 10
#6 Updated by Anonymous almost 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 902c71ef6316b63ebff64773769cff477604a646.
fixes #5537: it's possible to specify menu item url directly now