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
Get Updates on the Splunk Community!

Get Your Exclusive Splunk Certified Cybersecurity Defense Engineer at Splunk .conf24 ...

We’re excited to announce a new Splunk certification exam being released at .conf24! If you’re headed to Vegas ...

Share Your Ideas & Meet the Lantern team at .Conf! Plus All of This Month’s New ...

Splunk Lantern is Splunk’s customer success center that provides advice from Splunk experts on valuable data ...

Combine Multiline Logs into a Single Event with SOCK: a Step-by-Step Guide for ...

Combine multiline logs into a single event with SOCK - a step-by-step guide for newbies Olga Malita The ...