Dashboards & Visualizations

Issue while updating Splunk custom command permission from UI

Sidharda
Path Finder

Hello Experts,

While I am trying to make my custom Splunk command Global, I am unable to do so because of the below error.

Splunk could not update permission for resource admin/commandsconf [HTTP 500] Splunkd internal error; [{'type':'ERROR','code':None. 'text':"This handler does not support the 'edit' action and cannot be used for ACL modification."}]

Please help on this.

reed_kelly
Contributor

KLK

Same issue 9.1.2.

0 Karma

earlhelms
Path Finder

Same issue Splunk 8.0.7

BernardEAI
Communicator
Same issue on 8.1.4
0 Karma

ruman_splunk
Splunk Employee
Splunk Employee
This is a bug, since 6.6.0 apparently. I've tagged it to get included in docs known issues. SPL-173061.
 
0 Karma

sh1pit76
Explorer

I'm getting a similar error after upgrading to Splunk version 8.0.2.1. Would love to get an answer on this as well.

Splunk could not update permissions for resource data/lookup-table-files [HTTP 500] Splunkd internal error; [{'type': 'ERROR', 'code': None, 'text': "This handler does not support the 'edit' action and cannot be used for ACL modification."}]

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