Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rules for restricting access to resources by user, role and institution #146

Closed
sebdeleze opened this issue Feb 11, 2020 · 2 comments · Fixed by #228
Closed

Rules for restricting access to resources by user, role and institution #146

sebdeleze opened this issue Feb 11, 2020 · 2 comments · Fixed by #228

Comments

@sebdeleze
Copy link
Contributor

No description provided.

@sebdeleze
Copy link
Contributor Author

Could you provide me a first set of rules ?

@sebdeleze
Copy link
Contributor Author

As discussed, as a first step, we take the simple rules referenced in this document for covering this task.

@sebdeleze sebdeleze added 5 and removed 8 labels May 14, 2020
sebdeleze pushed a commit that referenced this issue Jun 16, 2020
* Creates a factory for managing permissions.
* Adds serializer and loader for deposit resources.
* Adds a deny access permission.
* Adds specific permissions decisions for all resources.
* Adds queries factories for filtering records in lists.
* Adds permissions results when serializing a record.
* Guesses user's organisation when creating a user record.
* Guesses user's organisation when creating a document record.
* Removes redirection to documents records when accessing administration.
* Adds permissions checks for adding resources when retrieving logged user by API.
* Removes organisation from user and document schema when logged user is not superuser.
* Adds missing role `publisher` in available roles.
* Removes `required` flag from marshmallow schema for users.
* Removes roles from editor when user is not at least admin.
* Restricts available roles in user editor when user is admin.
* Improves fixtures in tests.
* Closes #146.
* Closes #217.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant