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
Now that we have the application privileges in place, and we're reviewing elastic/kibana#19723 , we'll want to switch the kibana_user and kibana_dashboard_only_user roles to utilize the new application privileges and no longer have direct access to the .kibana* indices.
We'd like the kibana_user role to have the all privilege on * resources; and the kibana_dashboard_only_user role to have the read privilege on * resources.
It should be noted that we won't want to merge this change until elastic/kibana#19723 merges, or else we risk making existing users with the kibana_user roles non-functional.
The text was updated successfully, but these errors were encountered:
@kobelb this will prevent users from using kibana until kibana has also been upgraded if I understand correctly. I'm just pointing this out because we'll need to document this.
@kobelb this will prevent users from using kibana until kibana has also been upgraded if I understand correctly. I'm just pointing this out because we'll need to document this.
That's a good point, and something we should definitely document because I can't think of a way around this.
Uh oh!
There was an error while loading. Please reload this page.
Now that we have the application privileges in place, and we're reviewing elastic/kibana#19723 , we'll want to switch the
kibana_user
andkibana_dashboard_only_user
roles to utilize the new application privileges and no longer have direct access to the.kibana*
indices.We'd like the
kibana_user
role to have theall
privilege on*
resources; and thekibana_dashboard_only_user
role to have theread
privilege on*
resources.It should be noted that we won't want to merge this change until elastic/kibana#19723 merges, or else we risk making existing users with the
kibana_user
roles non-functional.The text was updated successfully, but these errors were encountered: