Knowledge Management

Reset knowledge object permissions to app default

merrelr
Path Finder

I'm working on cleaning up permissions for knowledge objects on our search head cluster. I noticed that if I create new knowledge objects and share them with the app their settings in local.meta don't have a line for 'access ='.

 

Default app permissions example

 

[savedsearches/test-perms]
export = none
owner = admin
version = 8.1.1
modtime = 1610106340.325106000

 

After manually changing permissions (even back to the default)

 

[savedsearches/test-perms]
access = read : [ admin ], write : [ admin ]
export = none
owner = admin
version = 8.1.1
modtime = 1610106459.558993000

 


but no matter what I do to objects that have had permissions set I can't seem to get them to exist without this line and just accept app default permissions. 

Does anyone know a safe way to reset a knowledge objects permissions to app defaults without directly modifying local.meta on the sh-cluster members?

Labels (1)
Tags (1)
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 ...