Release 4.3.7 RC1 - Wazuh UI Manual Testing - Kibana 7.10.2, 7.16.x, 7.17.x, WZD - Revision 4308 #4402
Assignees
Comments
Mayons95
changed the title
Mayons95
changed the title
4293 Infinite loop trying to check alerts index patterns after reinstalling Wazuh indexer
4337 Wrong path for Wazuh logo customization
4359 Fix modules settings persistence between updates
4346 TypeError in the browser's developer console
I don't see any type error on the console 4350 - Scenario 1 - Fixed errors in group reports
4350 - Scenario 2 - In Progress4181 Short refresh timeout on manager restartScreencast.from.16-08-22.15.27.00.webm4340 4.3.5 unable to execute SQL Query for Windows CIS Benchmark ViewScreencast.from.16-08-22.15.34.30.webm4277 -1 Centralized service to restart WazuhScreencast.from.16-08-22.15.44.06.webm4277 -2 Centralized service to restart WazuhScreencast.from.16-08-22.16.01.32.webm4349 wazuh.yml in-file documentation |
#4346 TypeError in the browser's developer console
wazuh.yml update #4349
Configuration
Ruleset
Peek.2022-08-17.11-38.webm
|
4293 Infinite loop trying to check alerts index patterns after reinstalling Wazuh indexer
4359 Fix modules settings persistence between updates
4337 Wrong path for Wazuh logo customization
4346 TypeError in the browser's developer console
4350 Fixed errors in group reports - Scenario: Error due to accessing a property of undefined**
4350 Fixed errors in group reports - Scenario: Missing agents in the agent in the group table of group report**
4181 Short refresh timeout on manager restart
4340 4.3.5 unable to execute SQL Query for Windows CIS Benchmark View
4277 Centralized service to restart Wazuh - Scenario: Install from Cluster Mode
4277 Scenario: Install from [Manager Mode]
4349 wazuh.yml in-file documentation |
4293 Infinite loop trying to check alerts index patterns after reinstalling Wazuh indexerGrabacion.de.pantalla.desde.17-08-22.11.56.00.webm4359 Fix modules settings persistence between updates
4337 Wrong path for Wazuh logo customization
4346 TypeError in the browser's developer console
4350 Fixed errors in group reports - Scenario 1Grabacion.de.pantalla.desde.17-08-22.11.20.39.webm4350 Fixed errors in group reports - Scenario 2 - 500 agents4181 Short refresh timeout on manager restartGrabacion.de.pantalla.desde.17-08-22.11.48.50.webm4340 4.3.5 unable to execute SQL Query for Windows CISGrabacion.de.pantalla.desde.17-08-22.11.27.41.webm4277 Centralized service to restart WazuhIn Management > Configuration - Manager ModeGrabacion.de.pantalla.desde.17-08-22.11.33.43.webmIn Management > Configuration - Cluster ModeGrabacion.de.pantalla.desde.17-08-22.11.38.08.webmIn Management > RulesGrabacion.de.pantalla.desde.17-08-22.11.43.57.webmIn Management > CDB ListsGrabacion.de.pantalla.desde.17-08-22.11.45.56.webm4349 wazuh.yml in-file documentation
|
4293 Infinite loop trying to check alerts index patterns after reinstalling Wazuh indexerhe.mp44359 Fix modules settings persistence between updates
4337 Wrong path for Wazuh logo customization
4346 TypeError in the browser's developer console
I don't see any type error on the console 4350 - Scenario 1 - Fixed errors in group reportsgroups.mp44181 Short refresh timeout on manager restartrestart.mp44340 4.3.5 unable to execute SQL Query for Windows CIS Benchmark Viewsearch.mp44277 Centralized service to restart Wazuhrestartvideo.mp44349 wazuh.yml in-file documentation |
16 tasks
4293 Infinite loop trying to check alerts index patterns after reinstalling Wazuh indexer
4337 Wrong path for Wazuh logo customization
4346 TypeError in the browser's developer console
I don't see any type error on the console 4350 - Scenario 1 - Fixed errors in group reports
4350 - Scenario 2 - In Progress4181 Short refresh timeout on manager restart
4340 4.3.5 unable to execute SQL Query for Windows CIS Benchmark ViewScreencast.from.18-08-22.12.02.36.webm4277 -1 Centralized service to restart WazuhScreencast.from.18-08-22.11.53.01.webm4277 -2 Centralized service to restart WazuhScreencast.from.16-08-22.16.01.32.webm4349 wazuh.yml in-file documentation |
Mayons95
changed the title
1 task
|
Test Finished |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Status legend:
⚫ - None
🔴 - Rejected
🟢 - Approved
In the case of 🔴, create and link the issue.
Change Log
All notable changes to the Wazuh app project will be documented in this file.
Wazuh v4.3.7 - Kibana 7.10.2, 7.16.x, 7.17.x - Revision 4308
Fixed
Wazuh.yml review: fixed link to web documentation, improved in-file documentation and fixed some grammatical errors. #4378 #4399
Fixed an error during the generation of a group's report, if the request to the Wazuh API fails #4350
Fixed a problem with the group's report, when the group has no agents #4350
Fixed path in logo customization section #4352
Fixed a TypeError in Firefox. Change the Get request that was made with a Kibana core.http.get(/api/check-wazuh) resource to the WzRequest.genericReq resource and it no longer fails, also add a test capture to public/plugin.ts that wraps the request and in case of failure, the error is detected when the browser does not work with the V8 engine. #4362
Fixed an error of an undefined username hash related to reporting when using Kibana with X-Pack and security was disabled #4358
Fixed persistence of the plugin registry file between updates #4359
Fixed searchbar error on SCA Inventory table #4367
Fixed a routes loop when reinstalling Wazuh indexer #4373
Fixed Wazuh restart UI #4365
Removed
Removed the use of manager_host field related to agent information of Wazuh API responses, which is obsolete #4350
Test Cases to execute
@Wazuh-Initialization
4293 Infinite loop trying to check alerts index patterns after reinstalling Wazuh indexer
Happy path steps:
Using a Wazuh stack deployment (Wazuh dashboard, Wazuh indexer, Wazuh server), configure and start de the components. The Wazuh indexer should be in an independent machine.
Access to Wazuh dashboard and navigate to Wazuh plugin, configure the API host to work as expected. Secure the index pattern related to Wazuh are created. Keep the browser tab in the Wazuh plugin.
Remove, reinstall and start the Wazuh indexer using the Wazuh install assistant following the next steps:
This could be reproduced removing elasticsearch or wazuh-indexer container and rebuild it again
Returns to the browser tab that has the Wazuh plugin and navigates to another plugin section. The plugin health check should run and it should finish each check successfully, then it should redirect to /overview plugin path and instantly should redirect to the /health-check path again.
4359 Fix modules settings persistence between updates
Manual
Same plugin version and revision, restart the plugin platform. The registry file should not be changed.
For different plugin versions or revisions, restart the plugin platform. The registry file should be rebuilt and keeps the host configuration.
Different plugin version or revision removes some extension of any host in the registry file, and restart the plugin platform. The registry file should be rebuilt and keeps the host configuration. The removed extension should be included in the host and have the default value.
4337 Wrong path for Wazuh logo customization
Given the user is in Wazuh Kibana App.
When the user navigate to Settings --> Configuration --> Logo Customization
Then on the Logo Customization section, ‘/usr/share/wazuh-dashboard/plugins/wazuh/public/assets/’ url of the path is displayed.
4346 TypeError in the browser's developer console
Given the user is in Wazuh Kibana App.
And The user opens the developer console of the dev tool on the browser
When the user navigates any modules outside Wazuh
And the user clicks the Home button
Then no error in the browser's developer console is displayed
4350 Fixed errors in group reports
Scenario: Error due to accessing a property of undefined
Given the user is in Wazuh Kibana App.
And Logged user in Management/Groups//Information, wait the time to the Wazuh API token expires.
When The user clicks on the "Export PDF" button.
Then The PDF should be generated without errors. Check the generated PDF.
Scenario: Missing agents in the agent in the group table of group report.
Given the user is in Wazuh Kibana App.
And the group with more than 500 agents.
When The user clicks on the "Export PDF" button.
Then The PDF should be generated without errors and it should contain all the agents in the group displayed in a table.
4181 Short refresh timeout on manager restart
Given the user is in Wazuh Kibana App
And the user navigates to Management --> Configuration
When the user selects the Edit Configuration link
Then the manager configuration XML file to edit is displayed
When the user finds and edits the vulnerability detector tag
And the user changes enable tag with No value
And the user selects the Save button
Then the manager configuration is saved
When the user selects the restart manager button
And the user confirms the restart manager
Then the wazuh app is restarted and the error is not displayed
4340 4.3.5 unable to execute SQL Query for Windows CIS Benchmark View
Given the user is in Wazuh Kibana App
And the user navigates to Modules --> SCA
When the user selects the agent
Then the inventory tab is displayed
When the user writes on the filter or search field
Then the dropdown options are displayed
And no error on the dropdown options is displayed
4277 Centralized service to restart Wazuh
Scenario: Install from Cluster Mode.
Given the user is in Wazuh Kibana App
And the wazuh app was installed on cluster mode
And the user navigates to management->configuration
When the user selects the Edit Configuration link
Then the manager configuration XML file to edit is displayed
When the user finds and edits the vulnerability detector tag
And the user changes enable tag with No value
And the user selects the Save button
Then the manager configuration is saved
When the user selects the restart manager button
And the user confirms the restart manager
Then the wazuh node is restarted
When the user navigates to Managements/Rules
Then the user is redirected correctly.
Scenario: Cluster/Manager installation
Given the user navigates to Management/Rules
When the user add a new rule file
And the user restart Wazuh
Then the user can navigate to another module.
Scenario: Install from Manager Mode.
Given the user is in Wazuh Kibana App
And the wazuh app was installed on Manager mode
And the user navigates to management->configuration
When the user selects the Edit Configuration link
Then the manager configuration XML file to edit is displayed
When the user finds and edits the vulnerability detector tag
And the user changes enable tag with No value
And the user selects the Save button
Then the manager configuration is saved
When the user selects the restart manager button
And the user confirms the restart manager
Then the wazuh app is restarted
And no error message is displayed
When the user navigates to management -> rules
Then the module section is displayed
And no health check is displayed
4349 wazuh.yml in-file documentation
Test Comment: This test is to check the documentation, so with one complete check it’s consider pass.
Access to: https://documentation.wazuh.com/current/user-manual/wazuh-dashboard/config-file.html
This URL should redirect you to the current version of Wazuh Documentation
Settings should be displayed:
checks.metaFields
checks.timeFilter
checks.maxBuckets
extensions.hipaa
extensions.nist
extensions.tsc
extensions.oscap
extensions.gcp
This setting allows hiding Wazuh for the specified roles. Related issue: wazuh/wazuh-kibana-app#3164
disabled_roles
Name for the sample alerts index
alerts.sample.prefix
cron related settings: these settings configure the behavior of background tasks performed by the App.
cron.prefix
cron.statistics.status
cron.statistics.apis
cron.statistics.interval
cron.statistics.index.name
cron.statistics.index.creation
cron.statistics.shards
cron.statistics.replicas
These settings are used in the agents' enrollment interactive helper.
enrollment.dns
enrollment.password
Custom logos
customization.logo.app
customization.logo.sidebar
customization.logo.healthcheck
customization.logo.reports
Settings should not be displayed
wazuh-version.*: deprecated since 4.3.0. To be removed completely.
api.selector: deprecated. To be removed.
admin: seems to be no longer used. I assume it's been deprecated.
timeout: default value is set to 8000. Actual value is 20000.
wazuh.monitoring.shards: default value is set to 2. Actual value is 1.
wazuh.monitoring.creation: default value is d (daily). Actual value is w (weekly).
The text was updated successfully, but these errors were encountered: