higlass / higlass/higlass-docker
superuser as admin - design for better authorization model
Open
- Dominant language
- Shell
- Stars
- 34
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
My understanding is when you create a superuser it basically creates a django admin account. For HiGlass this is used to (1) create other users, (2) maintain views, and (3) maintain projects. But I'm concerned about the security profile here wrt to django configuration in general and security maintenance vs application maintenance (projects and views). This needs a better authentication / authorization mechanism particularly for open internet usage.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.