-
Notifications
You must be signed in to change notification settings - Fork 182
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
Multiple unexpected Errors during Wazuh app session #5821
Comments
These looks like plugin initialization errors. All plugins initialize when a user tries to access the application. If the security plugin is enabled, some of them might fail due to an unauthorized error until the user actually logs in. This happens due to the actual design of the security features in the upstream platform. But there is more to it. Let's comment on each error:
Comes from the reportsDashboard plug-in from the upstream. We will open an issue to Opensearch if none exists already. This is an incorrectly managed error.
Comes from the security plug-in from the upstream. We will open an issue to Opensearch if none exists already. The error is managed, and the stack trace is useful information for developers.
This comes from Wazuh app. The error is managed, and the stack trace is useful information for developers. It appears when the plugin is initialized, but there is no session, or it has expired, so there is an unauthorized event. The stack trace helps to identify the code and state of the app. |
Description
Multiple error messages appear on console during a normal session with the Wazuh app.
It should be necessary to check the following warnings and ensure does not affect the product.
The text was updated successfully, but these errors were encountered: