Manage permissions via the web interface instead of config file #17
Labels
Milestone
Comments
lfkeitel
added a commit
that referenced
this issue
Mar 12, 2018
The old permission settings in the toml file will be accepted, but ignored. They're used to migrate to the new database driven system but after that they're not used. UI and API rights are separate as they were conceptually with the toml file. All users are in the "default" ui group and the "disable" api group unless set otherwise. The status API is still behind a flag as it requires the view debug permission.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently all permissions are managed statically via the configuration file and requires a restart of the web component to take effect. Instead, the permissions could be managed through the web interface and stored either in a flat text file and loaded on start (updating internal structures as changes are made) or saved to the database. This would require a new admin page, a map between strings and the permission constants, and a new HTTP path.
The text was updated successfully, but these errors were encountered: