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

Content security policy and 401 errors when login and logout the UI #4221

Closed
BelenValdivia opened this issue Jun 6, 2022 · 3 comments · Fixed by #4200
Closed

Content security policy and 401 errors when login and logout the UI #4221

BelenValdivia opened this issue Jun 6, 2022 · 3 comments · Fixed by #4200
Labels
qa/report QA Team: Reporting possible bug type/bug Bug issue

Comments

@BelenValdivia
Copy link

BelenValdivia commented Jun 6, 2022

Wazuh Elastic Rev Security
4.3.4 7.x 4305 Basic, ODFE, Xpack
Browser
Chrome, Firefox

Description
Console errors in the DEMO environment UI.

Steps to reproduce

  1. Login into Wazuh UI
  2. Navigate through the UI
  3. Logout

Expected Result

  1. I expect not to see errors in the console

Actual Result

  1. I see some errors in the console:
    • Content security policy error
    • 401 errors
Wazuh-.developer.console.errors.mp4
@gdiazlo
Copy link
Member

gdiazlo commented Jun 6, 2022

Related issue:

@snaow
Copy link
Contributor

snaow commented Jun 8, 2022

Fixed in: #4199

We had an error introduced that was causing the visualizations not to load in any of the App panels.
The issue above is supposed to fix this error, we will close this one when we double-check that everything is working correctly

Thanks for reporting.

@AlexRuiz7
Copy link
Member

The first error message is expected and generated by the platform, not us. In fact, it's informed that a single error message is expected on the log directly next to the first error.

On the other hand, once the PR was merged, the dashboard shows as it should, and the Type was not set error no longer shows up.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
qa/report QA Team: Reporting possible bug type/bug Bug issue
Projects
No open projects
Status: Done
4 participants