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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...