Knowledge Management

Rest api for authorization

dvg06
Path Finder

Hi Splunkers, 

Trying to disable certain capabilities from roles via rest api, but havent been successful yet. Please help.

What is the rest endpoint url that I should use to disable.

I tried something like https://127.0.0.1:8089/services/authorization/roles/power/capabilities/rtsearch/disable, but this is invalid end point. Splunk documentation has not been very helpful. 

dvg06
Path Finder

thanks @manjunathmeti 

I can update the capabilities using the above command.

But any idea how to delete this particular capability? what flag should I use instead of -d?

0 Karma

manjunathmeti
Champion

First, you can GET list of capabilities and remove the role from the list and POST it back.

0 Karma

manjunathmeti
Champion

You can use /authorization/roles/<rolename> enpoint to get and update capabilities of a role. Refer this https://docs.splunk.com/Documentation/Splunk/8.1.1/RESTREF/RESTaccess#authorization.2Froles.2F.7Bnam....

curl -k -u admin:changeme https://localhost:8089/services/authorization/roles/power -d capabilities=search 

 

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

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...