More granular permissions *for API keys*
Allow API keys to have much more granular permissions (i.e: only the functions one may need to do a certain task).
Also, add a security category in the form to report possible improvements for Atlas.
And a UI/UX one.
Carlos
shared this idea
-
Michael
commented
We also have a need for more granular permissions. To centrally monitor all configurations of our clusters, we want to use the API. We use the api to check whether audit is enabled and how audit is configured.
To check this, the api key must have project_owner or organization_owner permissions. This is very worrying from a security point of view, because it gives very powerful permissions. In this case it would be helpful to create a role with extended read permissions (>Organization Read Only).
I think that in the long run there is no way around the fact that users must be able to create their own roles.