#authentik and wazuh

1 messages · Page 1 of 1 (latest)

vital plover
#

Does anyone know if this guide is still valid?
https://integrations.goauthentik.io/monitoring/wazuh/

When opening the integration from Authentik I get the following issue.
https://imgur.com/a/sbRbyjj

If I omit the escape character in the ACS url then it get HTTP 401 response and can see the Wazuh.indexer reporting "Missing Authorization header"

Im glad to provide any logs if anyone is interested but I don't feel like just shouting out all the logs here.

bright horizon
#

@vital plover hi i was searching for support for the same topic. Wazuh changed the paths inside the container (idk why) so the documentation is out of date. Unfortunetelly i didn't got wazuh to work with authentik so far 🙁

vital plover
#

Got it working eventually, I removed the escape char. However there are some things in the guide that appears to not be current. You’ll have to add custom permissions for opensearch for the integration to work. I don’t currently have them available however I could get them to you tomorrow some time..✌️👀