Roles and permissions

Allow configuring roles and permissions with a good default set for the average school.

changed milestone to %1.0a1

added part::backend prio::1 type::feature labels

https://github.com/dfunckt/django-rules

changed milestone to %1.0a2

changed milestone to %1.0a3

COncerning media files, here is how to do permission checking and file delivery performantly:

https://wellfire.co/learn/nginx-django-x-accel-redirects/

https://github.com/johnsensible/django-sendfile

I think I found the permission framework I like best for this: https://django-authority.readthedocs.io/en/latest/create_custom_permission/

mentioned in issue #161 (closed)

Maybe we should divide this task in two parts:

1. Add basic permissions and decorators (admin/login/person-required)
2. Add an per-object permission system

As I understand it, we have decided that we require login for all views now. So we should enforce that by using a middleware. There is an approach called django-stronghold, but it seems not well maintained. We can use it or clone it, but in some way make login_required the default and instead decorate views that are public should there be any.

https://github.com/mgrouchy/django-stronghold

For the rest, I think that per-object permissions cover everything - every operation in AlekSIS should operate on an object, and the object should decide whether it grants access or not.

added workflow::discussing label

changed due date to January 24, 2020

changed due date to February 07, 2020

changed milestone to %2.0a2

unassigned @nik

changed due date to February 21, 2020

removed due date

added part::backend prio::1 type::feature workflow::discussing labels

created merge request !207 (merged) to address this issue

mentioned in merge request !207 (merged)

mentioned in issue AlekSIS-App-Chronos#45 (closed)

mentioned in commit c2439d02

closed via merge request !207 (merged)