Open lahwaacz opened 1 year ago
Hi @lahwaacz,
had the same problem some time ago. I think your formgrade-testcourse
role in addition needs the read:services!service=testcourse
scope to see all service properties. But not sure. I it does not work, I'll have a look at my setup where this (non-admin instructors) works.
Best regards,
Jens
Hi @jeflem, thanks for the hint! It fixed the problem, but I will leave this issue open for the developers to decide if this is worth adding to the documentation.
Thanks @jeflem for the answer. Is this fix also necessary for the docker example ?
I would say: yes, fix is necessary in demo_multiple_classes
. But did not test this.
The formgrade-course101
role in demo_one_class_multiple_graders
has the read:services...
scope, but the formgrade-...
roles in demo_multiple_classes
do not.
@brichet Please also update the documentation on Using nbgrader with JupyterHub – it uses an obsolete format for load_groups
and does not mention scopes at all.
@jeflem I confirm the need of scope read:services!service=testcourse
I had similar problem: non-admin users could not list courses. The log misses scope list:services
, however, adding it was not enough.
I have updated the wiki pages on my multi-grader / multiple-class show-case with the new configuration (jupyterhub 4.0.2, nbgrader 0.9.1).
Operating system
Arch Linux
nbgrader --version
nbgrader version 0.9.0
jupyterhub --version
(if used with JupyterHub)4.0.2
jupyter notebook --version
7.0.3
Expected behavior
The formgrader service should be accessible by admin and non-admin users alike.
Actual behavior
Traceback:
service
object for a non-admin user:service
object for an admin user:Steps to reproduce the behavior
I have the following jupyterhub config based on the one class, multiple graders use case:
The "instructor1" is an admin in JupyterHub, but "instructor2" is not. Formgrader is running as an externally-managed JupyterHub service.