-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
3
-
False
-
False
-
No
-
-
-
-
-
-
No
-
Undefined
-
No
-
Yes
-
-
MODH Sprint 15, MODH Sprint 16, MODH Sprint 17, MODH Sprint 18
As a RHODS admin, I need to be able to limit users' access based on defined user permissions so I can control access to RHODS functionality.
This story is to investigate how JupyterHub can manage authorization based on group membership. Currently, it reads users from a config map and gives access based on the user existing in that config map. We want JupyterHub to be able to handle groups from an OAuth provider like OpenShift Authentication so access rights within JupyterHub can restricted based on group membership. For example, standard RHODS users should not be able to add or remove users.
- relates to
-
RHODS-635 As a QE, I want to test users permissions in RHODS based on roles/groups
- Closed