-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Breaking change] kibana_user
role removed and replaced by kibana_admin
#81674
Comments
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
kibana_user
role removed and replaced by kibana_admin
Pinging @elastic/kibana-security (Team:Security) |
I'm going to remove the |
Change description
Which release will ship the breaking change?
8.0
Describe the change. How will it manifest to users?
The
kibana_user
role has been removed, and users should use thekibana_admin
role instead. Users who are still assigned thekibana_user
role will no longer be granted those privileges and will be unable to login and use Kibana.How many users will be affected?
There are likely a considerable number of deployments that are still using the
kibana_user
role. It was the primary method of granting users access to Kibana prior to Spaces and the granular RBAC work. Additionally, thekibana_admin
role was introduced mid-7.x.What can users do to address the change manually?
Use Kibana's user management to change all users who are granted the
kibana_user
role to now use thekibana_admin
role. Use Kibana's role-mapping management to change all role-mappings which assign thekibana_user
role to now assign thekibana_admin
role.How could we make migration easier with the Upgrade Assistant?
If we could automatically migrate users and role-mappings to use
kibana_admin
instead ofkibana_user
, it'd eliminate this burdenAre there any edge cases?
No
Test Data
Provide test data. We can’t build a solution without data to test it against.
Cross links
N/A
The text was updated successfully, but these errors were encountered: