github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 09:19:04 -04:00
Code Issues Projects Releases Packages Wiki Activity

[docs] improve recovery steps for 6.5 migration issue (#25761)

Browse source 
Fixes https://github.com/elastic/kibana/issues/25757

Just a couple tweaks to the recovery steps that mention the specific permissions necessary and instructions for using `kibana-keystore`.

[skip-ci]
This commit is contained in:
Spencer 2018-11-15 14:51:54 -08:00 • committed by GitHub
parent b8133ff063
commit 2c9727304b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/CHANGELOG.asciidoc
View file

@ -97,10 +97,11 @@ After upgrading from an older version of {kib} while using {security}, if you ge
+
1. Stop Kibana
2. Delete the `.kibana_1` and `.kibana_2` indices that were created
3. Create a new role in Elasticsearch that has the `all` permission for the `.tasks` index
3. Create a new role in Elasticsearch that has `create_index`, `create`, and `read` permissions for the .tasks index
4. Create a new user in Elasticsearch that has the `kibana_system` role as well as the new role you just created
5. Update `elasticsearch.username` and `elasticsearch.password` in kibana.yml with the details from that new user
6. Start Kibana
6. If using a Kibana secure settings keystore, remove keys `elasticsearch.username` and `elasticsearch.password` from the keystore using the `kibana-keystore` tool. Add these keys back to the keystore using the new user and password as values.
7. Start Kibana
+
This will be fixed in a future bug fix release, at which time you can go back to using the built-in `kibana` user.