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

Documentation Suggestion #60

Open
dave-safian-kyndryl opened this issue Feb 2, 2023 · 1 comment
Open

Documentation Suggestion #60

dave-safian-kyndryl opened this issue Feb 2, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@dave-safian-kyndryl
Copy link

In regards to configuring webhooks in github (github_webhooks.MD) you can use basic auth instead.

Advantages: HEC token isn't passed as part of the URL (which is visible and will get logged everywhere)
Does not require allowQueryStringAuth = true on the HEC Endpoint. In Splunk Cloud, you gotta get Splunk support to enable it even.

All that needs to change in the webhook configuration is:

AuthQueryToken:
https://YOUR SPLUNK URL:8088/services/collector/raw?token=THE TOKEN FROM ABOVE.

BasicAuth:
https://xxxxx:THETOKENFROMABOVE@YOUR SPLUNK URL:8088/services/collector/raw

Username doesn't matter (xxxxx). Token is used as the password for basic auth.

@dave-safian-kyndryl dave-safian-kyndryl added the enhancement New feature or request label Feb 2, 2023
@mcantu
Copy link

mcantu commented Apr 4, 2023

@dave-safian-kyndryl this has been driving me nuts! I'm using Splunk Cloud and couldn't figure out why in the world my webhook configuration wasn't working. I couldn't even modify the allowQuery portion, makes total sense that you have to contact support.

At least for now, with your suggestion, I got my webhooks to successfully deliver to my Splunk Cloud instance. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants