All Apps and Add-ons

Allow non-Splunk Admins to add the ServiceNow action to alerts

mjones1
Engager

We have this stood up and working...sort of.  Splunk Admins can configure alerts to add the "ServiceNow Incident Integration" action, and we can create Incidents in Splunk.

The problem is, we have a lot of development teams that create/maintain their own alerts in Splunk.  When they go to add this action, they're not able to select the account to use when configuring the action...because they don't have read permission to the account.  Even if an Admin goes in and configures the action, it won't work at run-time, because the alert runs under the owner's permissions...which can't read the credentials to use to call ServiceNow.

Has anyone else ran into this issue?  How can this be setup to allow non-Admins to maintain alerts?

Labels (2)
0 Karma
1 Solution

Rdm
Engager

I faced this same issue. Resolved it by adding list_storage_passwords capability to Non-admin Role

View solution in original post

0 Karma

mjones1
Engager

Yeah, that is the solution we ended up with as well.

0 Karma

Rdm
Engager

I faced this same issue. Resolved it by adding list_storage_passwords capability to Non-admin Role

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

 Are you ready to revolutionize your IT operations? As digital transformation accelerates, the demand for ...

Calling All Security Pros: Ready to Race Through Boston?

Hey Splunkers, .conf25 is heading to Boston and we’re kicking things off with something bold, competitive, and ...

Beyond Detection: How Splunk and Cisco Integrated Security Platforms Transform ...

Financial services organizations face an impossible equation: maintain 99.9% uptime for mission-critical ...