Security

Application level Admin access...

axcherukuri
Engager

Hi,

I was wondering if there is a way to provide admin access @ application level (all its objects) to a specific role instead of global admin access (admin_all_objects).

Thanks

Tags (1)

axcherukuri
Engager

found a solution for this.

  1. Define seperate indexes
  2. assign admin_all_objects accces to the role
  3. from command line add required role to write permissions. File: /etc/apps//metadata/default.meta

Sample default.meta

Application-level permissions

[]
access = read : [ * ], write : [ admin, power, myRole ]

EVENT TYPES

[eventtypes]
access = read : [ * ], write : [ admin, power, myRole ]
export = system

PROPS

[props]
access = read : [ * ], write : [ admin, power, myRole ]
export = system

TRANSFORMS

[transforms]
access = read : [ * ], write : [ admin, power, myRole ]
export = system

LOOKUPS

[lookups]
access = read : [ * ], write : [ admin, power, myRole ]
export = system

VIEWSTATES: even normal users should be able to create shared viewstates

[viewstates]
access = read : [ * ], write : [ * ]
export = system

Thanks

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...