Compatibility with OpenSearch 2.6.0

[AlexRuiz7]

Description

As Wazuh Dashboard is based on OpenSearch Dashboards, we need to ensure the UI compatibility with the next version of OpenSearch v2.6.0.

For that, we need to:

• Review the release notes of OpenSearch and OpenSearch Dashboards for this version.
• Identify improvements and potential impact on the UI.
• Develop a testing environment to verify our components would work under this new build.
• Test the latest Wazuh plugin in this new version.

Issues

• Agents evolution time picker does not close #5300
• Table Top 5 users in FIM::Dashboard overflows #5317

[AlexRuiz7]

Release notes and potential issues

2.5.0

Potential issues:

• [Table Visualization] Refactor table visualization using React and DataGrid component

Should not impact any existing functionality, but worth taking it into account when testing.

• [Table Visualization] Fix a problem with table visualizations that prevented URLs from being rendered correctly

URLs displayed in tables are now rendered correctly and not as strings. Some security concerns, read the pull request for more details.

Interesting issues:

• [CVE-2022-25912] Bump simple-git from 3.4.0 to 3.15.0
• [CVE-2022-35256] Bump node version from 14.20.0 to 14.20.1
• [CVE-2022-46175] Bump json5 version from 1.0.1 and 2.2.1 to 1.0.2 and 2.2.3
• [VisBuilder] Fix an issue that caused a crash when certain filters were added to a table visualization
• [VisBuilder] Fix errors throws when pipeline aggregations, like cumulative sum, were used in VisBuilder
• [VisBuilder] Create global data persistence for VisBuilder
• [VisBuilder] Introduce Redux store persistence
• [VisBuilder] Enable persistence for app filter and query without using state containers
• Documentation

2.6.0

Potential issues:

• None

Interesting issues:

• [CVE-2022-37599] Bump loader-utils from 2.0.3 to 2.0.4
• [CVE-2022-37603] Bump loader-utils from 2.0.3 to 2.0.4
• [CVE-2022-25860] Bump simple-git from 3.15.1 to 3.16.0
• [CVE-2022-25881] Resolve http-cache-semantics from 4.1.0 to 4.1.1
• [Security] Bump hapi/statehood from 7.0.3 to 7.0.4
• [CVE-2023-25166] Bump formula from 3.0.0 to 3.0.1
• [CVE-2020-36632] Bump flat from 4.1.1 to 5.0.2
• [CVE-2023-25653] Bump node-jose from 2.1.1 to 2.2.0
• [CVE-2022-24999] Resolve qs from 6.5.3 to 6.11.0
• [CVE-2022-25758] Bump node-sass from 6.0.1 to 7.0.3 and sass-loader from 10.2.1 to 10.4.1 to bump scss-tokenizer from 0.2.3 to 0.4.3
• [CVE-2020-24025] Bump node-sass from 6.0.1 to 7.0.3
• [Multiple DataSource] Add support for SigV4 authentication

[AlexRuiz7]

Development environment and testing

A development environment has been added in aff220a

The development version of Wazuh is installed correctly in development mode:

There is a visual problem in the Top 5 users table at FIM::Dashboard, as it overflows from the parent element. This happens in any resolution and browser.

No more problems have been found. All our unit tests pass.

Installing and testing in production

I've built a package of the plugin for OpenSearch Dashboards 2.6.0. It installs correctly, and everything seems to work as expected:

• Wazuh app version and platform version
  

• Modules directory
  

• Security events (dashboard)
  

• Security events (events)
  

• Agents overview dashboard
  

• Agent's dashboard
  

---

However, I found this error in the console when entering the app:

reportsDashboards.plugin.js:24 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'split')
    at _callee4$ (reportsDashboards.plugin.js:24:201073)
    at tryCatch (reportsDashboards.plugin.js:24:180012)
    at Generator.invoke [as _invoke] (reportsDashboards.plugin.js:24:183963)
    at Generator.next (reportsDashboards.plugin.js:24:181151)
    at asyncGeneratorStep (reportsDashboards.plugin.js:1:73707)
    at _next (reportsDashboards.plugin.js:1:74018)
    at reportsDashboards.plugin.js:1:74168
    at new Promise (<anonymous>)
    at reportsDashboards.plugin.js:1:73930
    at checkURLParams (reportsDashboards.plugin.js:24:202215)

We do not use this plugin and our reports work as expected, so we can omit this message.