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.

Sign up for GitHub

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

Release/v5.4.9: Fix HTTP ingester token name #1038

Merged
merged 4 commits into from
Jul 9, 2024
Merged

Release/v5.4.9: Fix HTTP ingester token name #1038

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f43e376
fix token name
ashnwade Jul 9, 2024
5e7968e
Merge pull request #1035 from ashnwade/fix-mistakes
michael-wisely-gravwell Jul 9, 2024
91f1e9c
Merge pull request #1036 from gravwell/release/v5.4.6
michael-wisely-gravwell Jul 9, 2024
e2b6bad
Merge pull request #1037 from gravwell/release/v5.4.7
michael-wisely-gravwell Jul 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ingesters/http.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -528,7 +528,7 @@ tag=gravwell syslog Appname==httpingester Message == "HEC request" Hostname

#### Token-Name

Many third party services which are designed to send data to a HEC compatible listener have been observed sending authentication tokens with various random names; the default expected authentication header structure is `Authentication: Splunk <token>`, but we have seen everything from "User" to "user_name". The `Token-Name` configuration parameter can override the Authorization header token name so that the HEC compatible listener can still authenticate and support third party services that do not adhere to the HEC guidance.
Many third party services which are designed to send data to a HEC compatible listener have been observed sending authentication tokens with various random names; the default expected authentication header structure is `Authorization: Splunk <token>`, but we have seen everything from "User" to "user_name". The `Token-Name` configuration parameter can override the Authorization header token name so that the HEC compatible listener can still authenticate and support third party services that do not adhere to the HEC guidance.

An example curl command that would authenticate with a `Token-Name` of `foobar` and a `TokenValue` of `soopersekrit` would be:

Expand Down