GUI permission error on the Agents Summary page
Uni AT
Dear Wazuh community,
Several of our users are reporting one or multiple intermittent error message(s) that pop up at the bottom right of the page AGENTS MANAGEMENT --> SUMMARY when they are accessing it. It doesn't prevent the users from obtaining the data, but it is quite annoying still.
The errors they usually get look like this:
The API call that is responsible for this error is the following one, and is located between other successful API calls (GET /agents/summary, etc):
When doing the same command to the Wazuh Server Dev Tools under the same account, we get a 403 unauthorized error:
This account comes with restricted rights: no actions such as add/remove/upgrade agents are allowed. In addition, RBAC is configured and they are not allowed to view all the agents, just the ones from the group they belong to.
However, I am not sure why even reading the upgrade status (e.g. a simple GET request) is forbidden with the permissions we have set.
I just tried to add the "task:status" action to the user's role but the permissions error persists:
Could you please say whether it is possible to either hide this error, or which specific permission we could add to fix this?
Thank you very much in advance,
Marcos Darío Buslaiman
The task:status permission alone may not be enough in this case, since the upgrade task query is also subject to RBAC restrictions for the agents involved.
If the user is intentionally not allowed to perform agent upgrades, we would not recommend granting additional upgrade-related permissions only to avoid this message.
At the moment, there is no specific configuration option to hide only this permission error. We already have an issue to improve this behavior in Wazuh Dashboard 5.0, specifically around permission validation for agent upgrade-related actions and how these authorization errors are presented in the UI.
https://github.com/wazuh/wazuh-dashboard-plugins/issues/8053
Therefore, if the user can access the expected agents correctly according to the configured RBAC policy, we recommend keeping the current restricted permissions rather than broadening them just to suppress this notification.
Regards!