You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had the issue where I set up wazuh_api_users and wazuh_api_credentials to the same values, set up the cluster and ended up getting ERROR3099 .
I've tested the system using:
curl -u <user>:<password> -k -X GET "https://wazuh-master.host:55000/security/user/authenticate?raw=true"
...and discovered that it does not work with my provided credentials, but it works fine with the default wazuh/wazuh username and password. Changing /usr/share/wazuh-dashboard/data/wazuh/config/wazuh.yml with these (default) credentials made the dashboard function normally.
In case it's important, my username was 2 character and my password was 15 characters, contains lower and uppercase characters, a number and the special symbol: č.
The text was updated successfully, but these errors were encountered:
I've had the issue where I set up
wazuh_api_users
andwazuh_api_credentials
to the same values, set up the cluster and ended up getting ERROR3099 .I've tested the system using:
...and discovered that it does not work with my provided credentials, but it works fine with the default wazuh/wazuh username and password. Changing
/usr/share/wazuh-dashboard/data/wazuh/config/wazuh.yml
with these (default) credentials made the dashboard function normally.As far as I can tell the code at https://github.com/wazuh/wazuh-ansible/blob/master/roles/wazuh/ansible-wazuh-manager/tasks/main.yml#L270 works fine, I have tried them manually and no error is emmited. Yet the custom credentials don't work. I can see my user created in the dashboard user interface. I do not know enough about how all of this works to understand where the issue is.
In case it's important, my username was 2 character and my password was 15 characters, contains lower and uppercase characters, a number and the special symbol:
č
.The text was updated successfully, but these errors were encountered: