You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tell us about your request. Provide a summary of the request and all versions that are affected.
There is a new feature in flight, which allows system indices to now be accessible similar to a regular index, to offload some super-admin work to a regular user. The idea behind this to mitigate escalation of privileges required to access a system index. Plugins currently assume the role of super-admin when accessing their system index, and are inherently trusted. This new feature sets up the base of service-accounts which once implemented can be associated with plugins and can then be granted access to their own system index.
Docs needed:
Document that this new feature is toggle-able by super-admin
Once enabled, super-admin along-with anyone that has the permission restapi:admin/roles to modify a role can now grant system-index permission to self/other users.
Security index is an exception to this and a permission to it cannot be granted.
Super-admin accepts the risk that once enabled this feature opens access to system indices, which may contain sensitive information, by a regular user.
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
@DarshitChanpura Thanks again for generating this doc issue. I've been reviewing related security issues and PRs to get better context of this change and how this new permission is used. I still can't tell if it was decided to create a new flag that enables this permission and a second to list an array of system indexes that can be accessed by someone with this permission. Is that still part of the plan here? If yes, has that been decided yet, the name of the new flags (settings)?
@DarshitChanpura Thanks for the answer. So this is the only new setting? There is NOT a second that allows you to specify individual system indexes that are turned on when enabled? I'm guessing not. But I want to confirm (for example, the suggestion made by cwperks in this comment: opensearch-project/security#2553 (comment). This idea is no longer in play, right?).
Last, is this setting made in config.yml or opensearch.yml?
So this is the only new setting? There is NOT a second that allows you to specify individual system indexes that are turned on when enabled? I'm guessing not. But I want to confirm (for example, the suggestion made by cwperks in this comment: opensearch-project/security#2553 (comment). This idea is no longer in play, right?).
Correct, there is only one setting and that is to toggle the feature.
Last, is this setting made in config.yml or opensearch.yml?
What do you want to do?
Tell us about your request. Provide a summary of the request and all versions that are affected.
There is a new feature in flight, which allows system indices to now be accessible similar to a regular index, to offload some super-admin work to a regular user. The idea behind this to mitigate escalation of privileges required to access a system index. Plugins currently assume the role of super-admin when accessing their system index, and are inherently trusted. This new feature sets up the base of service-accounts which once implemented can be associated with plugins and can then be granted access to their own system index.
Docs needed:
restapi:admin/roles
to modify a role can now grant system-index permission to self/other users.What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
Note: We are targeting 2.10 for feature release.
The text was updated successfully, but these errors were encountered: