Getting Data In

Which role allows for REST API KV Store Updates?

bofasplunkguy
Explorer

I have a dashboard linked to a JavaScript file which allows users to click a button that will pass updates to the KV Store. Therefore, I need to know the minimum amount of access I need to give to users so they can interact with this dashboard successfully.

I have been reading about the roles here: https://docs.splunk.com/Documentation/Splunk/latest/Security/Rolesandcapabilities#List_of_available_...

It seems like the role I should need is called "rest_properties_set" which is included in the user, power, and admin role. However, when testing my dashboard with just the user role, I get the following error:

[SPLUNKD] User 'kv_api_test' with roles { kv_api_test, user } cannot write: /nobody/kvStoreApp/collections/myKVStore { read : [ * ], write : [ admin, power ] }, export: app, removable: no

My user account is able to update the KV Store when I add the "rest_apps_management" role. However, this role is meant for admins, and the definition states it allows users to alter other apps and do far more than update the KV Store.

How can I restrict users to only be able to edit KV Store entries without giving any additional access?

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...