Menu/authorization: need alternative to rails controller centric authorization
|Assigned To:||Dmitri Dolguikh|
|Target version:||Sprint 23|
|Found in release:||Pull request:|
|Velocity based estimate||-|
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".