fine-grained access controls #296
Labels
arkime
Relating to Malcolm's use of Arkime
enhancement
New feature or request
nginx
Relating to Malcolm's use of nginx
opensearch
Relating to Malcolm's use of OpenSearch
security
Related to issues with bearing on the security of Malcolm itself
Milestone
Malcolm doesn't currently have any kind of fine-grained access controls. In other words, if you're a logged in user you can pretty much do whatever all the other logged-in users can do.
This is a feature that will be important as the project gets bigger. But we have a few things to consider:
This is a pretty big feature but would be of value. I think that, at least initially it should be pretty basic: basically something like the concept of a "read-only" user (can view all data, but not upload or write data) vs. a "read-write" user (can do both). It would be really nice if we could handle this entirely at the NGINX level in nginx.conf somehow, (see
limit_except
in this example).The text was updated successfully, but these errors were encountered: