Custom Query (2152 matches)
Results (1102 - 1104 of 2152)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#1097 | fixed | Sidebar hideable | dread | dread |
Description |
The web interface has a sidebar (#primary) which should be hidden in some pages. This is for QA extension and useful for package new and edit pages. Must be compatible with DGU theme. |
|||
#1095 | fixed | add way to pass in schema to logic layer. | kindly | kindly |
Description |
We need a way to pass in schemas to the logic layer to deal with edge cases. |
|||
#1094 | duplicate | [super] Refactor the Auth System | thejimmyg | thejimmyg |
Description |
Here are some proposed changes related to CKAN's authorization system - they aren't very big, but should provide for some forthcoming use cases including #787. Two man reasons for the changes are:
The first two changes revolve around the is_authorized method, which is called by the logic layer to ask whether a particular user (e.g. Bob) is allowed to do a certain action (e.g. edit) on a certain object (e.g. Package).
which *overrides* the current call with its own implementation (note: in previous discussions we have considered allowing a chain of plugins, no longer!) Reason: authorization can be completely delegated to another system (or partially)
but for action=create_package, the object supplied is System, and for action=edit the object supplied is the package. Instead action should always be the string name of a function in the logic layer and object should always be the object passed to that function. This means our auth system is based around the actual actions we are performing (rather than a model them) and with the actual data that forms the action (rather than a related object). You never need a System object in this model.
Although this sounds a bit radical we already have auth extensions. Read-only CKAN Web UI(Additional requirement from #764) Whilse using CKAN web interface, you are not tempted to edit stuff:
|