Skip to content
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

Add manage_aliases, manage_templates and open_close_indices as separate privileges #29732

Open
elasticmachine opened this issue Feb 10, 2017 · 2 comments
Labels
>enhancement :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC Team:Security Meta label for security team

Comments

@elasticmachine
Copy link
Collaborator

Original comment by @ppf2:

manage
All monitor privileges plus index administration (aliases, analyze, cache clear, close, delete, exists, flush, mapping, open, force merge, refresh, settings, search shards, templates, validate, warmers)

The manage privilege today includes the ability to perform destructive actions like delete index.

Since delete_index is already a separate privilege, this is a request to remove delete_index from manage so that customers can give manage role to users who will be setting up the schema/mappings,templates,aliases, without also giving them the ability to delete the index.

And if they need delete_index, they can separately add it to the role.

Please consider this for 5.0. The customer is working around this on 2.x using the no-longer-recommended granular setting for action level privileges (which has already been removed from the product on 5.0).

@elasticmachine
Copy link
Collaborator Author

Original comment by @jaymode:

@bizybot I think this might be another good issue for you to look into

@elasticmachine
Copy link
Collaborator Author

Original comment by @bizybot:

@jaymode Sure will start looking into it. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement :Security/Authorization Roles, Privileges, DLS/FLS, RBAC/ABAC Team:Security Meta label for security team
Projects
None yet
Development

No branches or pull requests

3 participants