|
@@ -84,7 +84,7 @@ Alternatively, you can set the initial passwords for the built-in users by using
|
|
|
the *Management > Users* page in {kib} or the
|
|
|
<<security-api-change-password,change password API>>. These methods are
|
|
|
more complex. You must supply the `elastic` user and its bootstrap password to
|
|
|
-log into {kib} or run the API. This requirement means that you cannot use the
|
|
|
+log in to {kib} or run the API. This requirement means that you cannot use the
|
|
|
default bootstrap password that is derived from the `keystore.seed` setting.
|
|
|
Instead, you must explicitly set a `bootstrap.password` setting in the keystore
|
|
|
before you start {es}. For example, the following command prompts you to enter a
|
|
@@ -96,7 +96,7 @@ bin/elasticsearch-keystore add "bootstrap.password"
|
|
|
----------------------------------------------------
|
|
|
|
|
|
You can then start {es} and {kib} and use the `elastic` user and bootstrap
|
|
|
-password to log into {kib} and change the passwords. Alternatively, you can
|
|
|
+password to log in to {kib} and change the passwords. Alternatively, you can
|
|
|
submit Change Password API requests for each built-in user. These methods are
|
|
|
better suited for changing your passwords after the initial setup is complete,
|
|
|
since at that point the bootstrap password is no longer required.
|