Splunk Dev

UI-Toolkit React-App unable to fetch REST-Endpoint "services/admin/LDAP-groups"

TheEggi98
Path Finder

Hello Splunk Community,

to get into ReactJS and the Splunk UI-Toolkit i created a small App with a Component, thats fetching the Splunk-Roles and the LDAP-groups from splunks REST-API for easy mapping of matching groups and roles.

Fetching of the roles work, but the groups dont.

Codeside i fetch against '/splunkd/services/admin/LDAP-groups?output_mode=json'
That respond with 303 see other and refers to
'<locale>/splunkd/services/admin/LDAP-groups?output_mode=json'
where i get the 404 Page not Found response.

Searching for the requestId shows following:
proxy:132 - Resource not found: services/admin/LDAP-groups
error:321 - Masking the original 404 message: 'Resource not found: services/admin/LDAP-groups' with 'Page not found!' for security reasons

My User has the change_authentication capability, so theoretically it should work.
Am i doing something wrong? Or is that endpoint denied by default if its not splunk itself?

 

 



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