inveniosoftware / inveniosoftware/flask-resources

permissions: how are they handled

Open
#8 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
3
Forks
22
PR merge metrics
No merged PRs in 30d

Description

# CHANGE OF IDEAS FROM DISCUSSION. DO NOT TACKLE ISSUE.

currently the `RequestResourceCtx` has a `permission_action` attribute, but it is not used anywhere.

No permission scheme is implemented. Some resources might need the record itself (which only comes into knowledge at the controller level), therefore maybe different level of permissions are needed (e.g. resource_permissions and controller_permissions).

Some ideas that came from the RFC:

- Authentication will happen on the view. This means that the `resource_requestctx` will be populated with the user needs.
- Authoritzation will happen on the controller. It is the one that has access to the record, the db, the ES indexes/filters, etc.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.