Splunk Dev

why does loadjob fail producing the message: Error in 'SearchOperator:loadjob': error accessing https xxxx statusCode=403, description=Forbidden

rphillips_splk
Splunk Employee
Splunk Employee

loadjob returning statusCode=403, description=Forbidden when a user without admin role calls a search artifact created by a user with admin role. This works with 6.3.4. but in 6.3.5 produces the following error:

Error in 'SearchOperator:loadjob': error accessing https://127.0.0.1:8089/servicesNS/some-admin/search//saved/searches/mysearchtest/?output_mode=json, statusCode=403, description=Forbidden

Tags (1)
0 Karma

rphillips_splk
Splunk Employee
Splunk Employee

This is a known bug (SPL-123305) in 6.3.5 which is fixed in 6.3.6 and 6.4.2

as a workaround you can call the search artifact by using the 'nobody' user like:
| loadjob savedsearch="nobody:search:mysearchtest"

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Meet Splunk Observability Studio: AI-Assisted OpenTelemetry Instrumentation Without ...

Instrumentation is usually the last step or even an afterthought when building out a project. The feature ...

Federated Search for Cisco Security and Analytics Logging (SAL) is now GA on Splunk ...

Federated Search for Cisco  Security Analytics and Logging (SAL) is now generally available as part of the ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Join us for a demo-driven look at how ...