Dashboards & Visualizations

After setting up the HTTP Event Collector on a heavy forwarder, why am I getting error "token is required" when submitting events?

a212830
Champion

Hi,

I was able to get the HEC up and running on a HFW, but now when I submit an event, I get "token is required", even though I'm passing a token.

curl -k https://myserver.com:8088/services/collector/event -H "Authorization Splunk: 7E36213E-03E1-4246-93B9-81931D303A58" -d '{"event": "hello world"}'

Anyone run into this?

1 Solution

a212830
Champion

Never mind: got it:

curl -k https://myserver.com:8088/services/collector/event -H 'Authorization: Splunk 7E36213E-03E1-4246-93B9-81931D303A58' -d '{"event": "hello world2"}'

View solution in original post

a212830
Champion

Never mind: got it:

curl -k https://myserver.com:8088/services/collector/event -H 'Authorization: Splunk 7E36213E-03E1-4246-93B9-81931D303A58' -d '{"event": "hello world2"}'

sloshburch
Splunk Employee
Splunk Employee

Converted your post to answer so you can mark it as accepted.

For other folks who run into the same thing, was the issue just that the header is Authorization not Authorization Splunk and therefore once you moved the : after Authorization it all worked?

Get Updates on the Splunk Community!

Fall Into Learning with New Splunk Education Courses

Every month, Splunk Education releases new courses to help you branch out, strengthen your data science roots, ...

Super Optimize your Splunk Stats Searches: Unlocking the Power of tstats, TERM, and ...

By Martin Hettervik, Senior Consultant and Team Leader at Accelerate at Iver, Splunk MVPThe stats command is ...

How Splunk Observability Cloud Prevented a Major Payment Crisis in Minutes

Your bank's payment processing system is humming along during a busy afternoon, handling millions in hourly ...