Splunk Search

Permissions scheduled searches

tawollen
Path Finder

I have a user that is scheduling a saved search and has results get sent to multiple users. When the users click on the link included in the email they get prompted to log into splunk and immediately. get a 403 error "AuthorizationFailed: [HTTP 403] Client is not authorized to perform requested action; None"

If they just log into splunk and run the search, they get results fine. They have the same roles as the person creating the search. Are the saved search results only accessible by the owner of the search? As admin I can see them of course.

Tags (3)
1 Solution

Ellen
Splunk Employee
Splunk Employee

This was a known issue (SPL-41061) reported under 4.2.1 and 4.2.2

It is targeted to be fixed in the next maintenance release.

View solution in original post

Ellen
Splunk Employee
Splunk Employee

This was a known issue (SPL-41061) reported under 4.2.1 and 4.2.2

It is targeted to be fixed in the next maintenance release.

jbsplunk
Splunk Employee
Splunk Employee

I ran into this and even with the saved search shared globally and read permission granted to the role which my user was assigned, I continued to get a 403. The only way I found to resolve this was by editing $SPLUNK_HOME/etc/apps//metadata/local.meta and changing the owner from the user who created the search to nobody. I validated the permissions of the saved search were set to allow my users role to read, then reloaded the saved searches via

http://mysplunkserver:port/en-US/debug/refresh?entity=admin/savedsearch

After that I was able to access the results.

Stephen_Sorkin
Splunk Employee
Splunk Employee

You should verify that the users encountering this problem are in the "read" ACL for the particular saved search object. To check, visit manager, check the specific saved search object, click on permissions and verify that any role for the users having the problem has read permissions.

If this is the case, the next step in diagnosing is to look at the search index=_internal source=*splunkd_access.log status=403 and determine which specific URL is returning the error.

tawollen
Path Finder

This looks similar to the following post: http://answers.splunk.com/questions/10946/authorizationfailed-http-403-when-clicking-on-the-link-in-...

It sounds like it was fixed in 4.1.6, we are running 4.2 I wonder if it broke again?

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...