Security

Splunk Search Head locking accounts out

walsborn
Path Finder

Hello,

I'm new to the Splunk Admin role and have a distributed environment. I have a single search head in a cluster that keeps locking an account out. We use LDAP to authenticate into Splunk and this search keeps attempting log a user in, even when they are not attempting to log in. Any idea how to fix this?

Labels (1)
0 Karma

codebuilder
Influencer

Splunk and LDAP are a finicky beast. The default depth of validation is 1000. Additionally, if a LDAP user is attached to more than one Splunk role, the first one that validates terminates further validation. Meaning, if I have a valid LDAP/AD account, but have more than one Splunk account, the first one wins. Or, if I have both a valid LDAP and Splunk account, but fall beyond the default 1000 search limit, I'll never validate, since Splunk will timeout (by default settings) before finding me.

----
An upvote would be appreciated and Accept Solution if it helps!
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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...