-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[META] Document fine-grained access control permissions needed for each client call #194
Comments
This could live in the API spec and both the comments and documentation could be generated from that. |
I'm moving this to opensearch-api-specification. |
Each API operation can be accompanied by a |
We can also always add a |
That is the idea, BUT: Whatever route we go, we need to specify whether the permission is under cluster_permissions or index_permissions. You can (and sometimes have to) add indices:* permissions at the cluster level. I admit to being completely confused about where to put, e.g. indices:write/data/bulk. By Cluster level, I mean cluster_permissions in the FGAC policy:
|
This is a generic comment, across clients.
I often stumble when trying to make API calls, to understand the needed permissions under fine-grained access control. The problem is made somewhat worse, and somewhat better, with action groups. Mapping the action groups to what they actually do is made easier by this page https://opensearch.org/docs/latest/security/access-control/default-action-groups/. But even that doesn't go all the way, since I don't know what API calls are under the client calls.
For each client, and each API, can we document the permissions (not the action group) required to execute that API.
If we can add comments to the individual clients' methods, we should be able to auto-generate this documentation. Either way, we need to put the information somewhere.
The text was updated successfully, but these errors were encountered: