We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Splunk input plugin token validation is case-sensitive, the Splunk HEC is not. It should be consistent.
To Reproduce
docker run -d --rm -p 8088:8088 -e "SPLUNK_START_ARGS=--accept-license" -e "SPLUNK_PASSWORD=whatever" -e "SPLUNK_HEC_TOKEN=ftooken" --name splunk splunk/splunk:latest
pipeline.yml
service: http_server: on pipeline: inputs: - name: dummy dummy: '{"message": "a message"}' outputs: - name: splunk alias: splunk_pccs_standard tls: on tls.verify: off host: <YOUR_SPLUNK_IP> port: 8088 splunk_token: ftooken match: '*'
The output will have no issues and will send the logs to the Splunk container.
Now change the token in the pipeline.yml to Ftooken (changed the first letter to uppercase) and restart the Fluent Bit output plugin.
Ftooken
The output is just the same, no issues.
Stop the Splunk container and start Fluent Bit with the following configuration:
fluent-bit.yml
service: log_level: debug pipeline: inputs: - name: splunk splunk_token: 'ftooken' port: 8088 outputs: - name: stdout match: '*'
Now, disable the tls in the output plugin, revert back the change in the token and restart the Fluent Bit output plugin.
The output in the Fluent Bit input side, will display the received records.
Now change the token in the pipeline.yml to Ftooken as we did before.
The output in the Fluent Bit output side will display the following error:
[2024/10/23 19:01:27] [ warn] [output:splunk:splunk_pccs_standard] http_status=401: error: unauthorized
The input plugin will display this error:
[2024/10/23 19:01:27] [ warn] [input:splunk:splunk.0] wrong credentials in request headers
Expected behavior
The Splunk input plugin should behave like the Splunk HEC.
Your Environment
Version used: 3.1.9
Configuration: in the steps to reproduce.
Filters and plugins: in_splunk
The text was updated successfully, but these errors were encountered:
cosmo0920
Successfully merging a pull request may close this issue.
Bug Report
Splunk input plugin token validation is case-sensitive, the Splunk HEC is not. It should be consistent.
To Reproduce
Issue reproduction
pipeline.yml
The output will have no issues and will send the logs to the Splunk container.
Now change the token in the
pipeline.yml
toFtooken
(changed the first letter touppercase) and restart the Fluent Bit output plugin.
The output is just the same, no issues.
Stop the Splunk container and start Fluent Bit with the following configuration:
fluent-bit.yml
Now, disable the tls in the output plugin, revert back the change in the token and restart the Fluent Bit output plugin.
The output in the Fluent Bit input side, will display the received records.
Now change the token in the
pipeline.yml
toFtooken
as we did before.The output in the Fluent Bit output side will display the following error:
The input plugin will display this error:
Expected behavior
The Splunk input plugin should behave like the Splunk HEC.
Your Environment
Version used: 3.1.9
Configuration: in the steps to reproduce.
Filters and plugins: in_splunk
The text was updated successfully, but these errors were encountered: