-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
3.0.5: output:splunk: Error http_status=401 Token is required #8867
Comments
Please provide your full configuration |
output plugin [OUTPUT] |
we are also facing same issue... 3.0.4 had lot of warning noise so upgraded to 3.0.5 which gave us "Token is required" error, despite of providing splunk_token in output config [2024/05/24 22:02:24] [debug] [output:splunk:splunk.0] Could not find hec_token in metadata |
I am looking into this. |
…token behavior (fix #8867) In the previous Splunk metadata fix, I introduced an issue where the metadata auth header was always set even if the metadata was not there, the code was generating an emptry string which leads to skip the classic splunk_token auth mechanism. This patch corrects the recent bug by validating first and returning a proper NULL when metadata auth header (hec_token) is not there. Signed-off-by: Eduardo Silva <[email protected]>
I have pushed #8873 to fix this issue. |
Hey @edsiper |
@rchopd |
Thanks a lot.. will test it once available and let you know our findings |
…token behavior (fix fluent#8867) In the previous Splunk metadata fix, I introduced an issue where the metadata auth header was always set even if the metadata was not there, the code was generating an emptry string which leads to skip the classic splunk_token auth mechanism. This patch corrects the recent bug by validating first and returning a proper NULL when metadata auth header (hec_token) is not there. Signed-off-by: Eduardo Silva <[email protected]> Signed-off-by: Markus Bergholz <[email protected]>
We are using v3.1.9, but we are still (or again?) getting these debug messages, even though we did specify a valid splunk_token. [2024/11/08 11:26:48] [debug] [output:splunk:splunk.1] Could not find hec_token in metadata |
With 3.0.5 getting below error.
[2024/05/24 05:47:13] [ warn] [output:splunk:splunk.16] http_status=401:
{"text":"Token is required","code":2}
The text was updated successfully, but these errors were encountered: