-
Notifications
You must be signed in to change notification settings - Fork 104
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
Alerts should be visible to users who have access to the tenant #119
Comments
Another addition to this, when choosing your own index then the list displaying the indices should be limited to your tenant only besides you are an admin as described here #139 Generally an admin should be able to see everything. |
@aimtsou Currently, OpenSearch-Dashboard-tenancy is for OpenSearch-Dashboard objects like dashboard, saved queries and few more. Alerting objects are not OpenSearch-Dashboard objects, you can group users using permissions/roles/backend roles while using Alerting. There is no plan to extend OpenSearch-Dashboard-tenancy to OpenSearch constructs like Alerting. |
But permissions in Alerting allow read/write to users, they do not allow index-based usage. |
Hi @brijos and @skkosuri-amzn, this enhancement of Alerting plugin could be great for us as well. Do you have any update concerning the backlog of this feature ? |
@JujuElk, like @skkosuri-amzn had mentioned, OpenSearch-Dashboard-tenancy is for OpenSearch-Dashboard objects like dashboard, saved queries and few more, but alerting objects are not OpenSearch-Dashboard objects and are OpenSearch objects. For this enhancement to be supported, the security plugin needs to connect with OpenSearch Dashboard's tenants to allow OpenSearch objects have different access control on OpenSearch-Dashboards using tenants. |
Is your feature request related to a problem? Please describe.
Since we have the multi-tenancy it will be important for each user in the alerting plugin(dashboards, monitors, destinations) to be able to define the options and has access to rules for the tenants that he belongs to. Consequently:
Describe the solution you'd like
Alerting package should belong only to the users of each tenant. If user1 has access to tenant1 then he sees the alerts configured for tenant1. If user1 has access to tenant1 and to tenant2, according to which tenant he has chosen, then considering his rights he is able to see and modify the alerts for this specific tenant.
Describe alternatives you've considered
No alternatives at the moment but we consider this an important enhancement
The text was updated successfully, but these errors were encountered: