Security

Problem with scripted authentication

sgp0637
Engager

We are using scripted authentication in Splunk using credentials of a central system. This works fine for 4 users out of 5 who have same role, same privileges and same index assigned.

However for one user, splunk web throws *500 Internal Server Error *. After enabling the debug, the scripted authentication is 'successful' including all three functions ie; userLogin,getUserInfo,getUsers. However, once its submitted to splunkd, it throws the error AdminHandler:AuthenticationHandler - Insufficient permissions to list user:<username>

The user has exactly same privileges as others.

Please share if you have experienced same issue and a possible solution if any.

Thanks

0 Karma
1 Solution

renjith_nair
Legend

Check if the user login as a space at the beginning or end.

---
What goes around comes around. If it helps, hit it with Karma 🙂

View solution in original post

0 Karma

renjith_nair
Legend

Check if the user login as a space at the beginning or end.

---
What goes around comes around. If it helps, hit it with Karma 🙂
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 ...