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

[Alerting] Update alerting feature privilege to allow subfeature privilege separation #99940

Closed
ymao1 opened this issue May 12, 2021 · 1 comment · Fixed by #100127
Closed
Assignees
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Theme: rac label obsolete

Comments

@ymao1
Copy link
Contributor

ymao1 commented May 12, 2021

As part of this issue, we have refactored the alerts authorization client to provide a generic consumer/producer based RBAC authorization on alerting entities (currently rule and alert). In order to support the subfeature privilege model, where for example, users may have read privileges on Alerting (Rules & Alerts) but be given elevated subfeature privilege to update alerts, we need to update the alerting feature privilege schema to handle separated feature strings for rules and alerts.

@ymao1 ymao1 self-assigned this May 12, 2021
@ymao1 ymao1 added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Theme: rac label obsolete labels May 12, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Theme: rac label obsolete
Projects
None yet
3 participants