Skip to content
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

Lack of Information about changing password in Multi-node Wazuh Installation deployed using Docker #6551

Closed
pro-akim opened this issue Sep 25, 2023 · 1 comment · Fixed by #6555
Assignees
Labels
level/task Task issue qa_known Issues that are already known by the QA team type/bug Bug issue

Comments

@pro-akim
Copy link
Member

pro-akim commented Sep 25, 2023

In https://documentation-dev.wazuh.com/v4.5.3-rc1/deployment-options/docker/wazuh-container.html

When attempting to change the password in a multi-node Wazuh installation using Docker, there is a lack of specific information regarding the variables that need to be replaced.

In a multi-node installation, the information regarding which changes need to be made on which nodes/hosts and the exact steps to follow may not be clear. The existing information is oriented towards making modifications in a single-node installation, where it correctly specifies what information needs to be modified and in which file it is located.

For example:
https://documentation-dev.wazuh.com/v4.5.3-rc1/deployment-options/docker/wazuh-container.html#setting-the-new-password

In the step: Open the docker-compose.yml file. Change all occurrences of the old password with the new one.
I case that I have a master and many workers, which hash should I change...

In the step: Run docker ps and note the name of the Wazuh indexer container. For example, single-node-wazuh.indexer-1.
It is not specified, in case there are many indexers, in which one should be done the steps to set the variables and reinitialize the process with:

bash /usr/share/wazuh-indexer/plugins/opensearch-security/tools/securityadmin.sh -cd /usr/share/wazuh-indexer/opensearch-security/ -nhnv -cacert  $CACERT -cert $CERT -key $KEY -p 9200 -icl
@pro-akim pro-akim added level/task Task issue type/bug Bug issue labels Sep 25, 2023
@pro-akim pro-akim added the qa_known Issues that are already known by the QA team label Sep 25, 2023
@wazuhci wazuhci moved this to Triage in Release 4.5.3 Sep 25, 2023
@wazuhci wazuhci removed this from Release 4.5.3 Sep 25, 2023
@wazuhci wazuhci moved this to Triage in Release 4.5.3 Sep 25, 2023
@teddytpc1 teddytpc1 assigned teddytpc1 and davidcr01 and unassigned teddytpc1 Sep 26, 2023
@davidcr01 davidcr01 linked a pull request Sep 26, 2023 that will close this issue
7 tasks
@wazuhci wazuhci moved this from Triage to In progress in Release 4.5.3 Sep 26, 2023
@pro-akim
Copy link
Member Author

pro-akim commented Sep 26, 2023

Update

Information upgraded.

@wazuhci wazuhci moved this from In progress to Pending review in Release 4.5.3 Sep 26, 2023
@wazuhci wazuhci moved this from Pending review to Pending final review in Release 4.5.3 Sep 27, 2023
@github-project-automation github-project-automation bot moved this from Pending final review to Done in Release 4.5.3 Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue qa_known Issues that are already known by the QA team type/bug Bug issue
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants