-
Notifications
You must be signed in to change notification settings - Fork 363
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
Update documentation for distributed environment #7370
Update documentation for distributed environment #7370
Conversation
PR UpdateNow it is not necessary to add a new user to the API users section. Wazuh manager uses the indexer admin user to change the Filebeat password. Also, when changing passwords in the dashboard, it will not be necessary to manually reset it, it will be done in the script itself. Documentation changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor changes, GJ
Co-authored-by: Carlos Bordon <[email protected]>
Changes commited |
@@ -99,6 +99,7 @@ If you use the tool in an all-in-one deployment, it automatically updates the pa | |||
|
|||
If you want to change the password for a Wazuh manager API user, run the script on a Wazuh server node and use option ``-A, --api``. Alternatively, you can change the Wazuh manager API passwords following the instructions in the :doc:`Securing the Wazuh API </user-manual/api/securing-api>` documentation. | |||
|
|||
.. note:: If you want to change the password for Filebeat in the Wazuh server, you don't need to use option ``-A, --api``. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Enaraque More useful would be to say what to do rather than what not to do. And I don't see the need to use a note here. Just a paragraph like the previous ones would be ok.
@@ -179,7 +198,7 @@ The options ``-au`` and ``-ap`` are necessary to change the passwords for the AP | |||
Changing the passwords in a distributed environment | |||
--------------------------------------------------- | |||
|
|||
Follow the instructions below to change the passwords for all the Wazuh indexer users as well as the Wazuh manager API users. | |||
Follow the instructions below to change the passwords for all Wazuh indexer users, Wazuh manager API users, and the Wazuh dashboard user. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "Wazuh dashboard user" isn't evident from reading the introduction. Does it mean wazuh-wui
? admin
? kibanaserver
? Other?
|
||
#. Update the ``/usr/share/wazuh-dashboard/data/wazuh/config/wazuh.yml`` configuration file with the new `wazuh-wui` password generated in the second step. | ||
#. Again, on your `Wazuh dashboard node`, run the following command to update the *wazuh-wui* password in the Wazuh dashboard keystore. Replace ``<WAZUH-WUI_PASSWORD>`` with the random password generated in the second step. Use the ``-A`` or ``--api`` option to change the password for the ``wazuh-wui`` user in the Wazuh dashboard node. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The second step generates more than one password. Do we mean Wazuh API user wazuh-wui
password?
Description
The goal of this PR is to upload the documentation from the password management section.
In this update, new information has been added to the part related to the distributed environment:
kibanaserver
andwazuh-wui
passwords with the script, so there is no need to change them manually.Documentation changes
Changes in password management