Security

LDAP Filter Adding Distinguished Name (DN)

ryan_t_gavin
New Member

We've been struggling to set up Splunk to use LDAP authentication for a while now. After finally getting it to bind successfully, it lists the groups when I map roles; however, when I log in as a user under a mapped role + group combo, it does not work. The DEBUG logs show the LDAP server returned no entries in search for DN="ou=Groups,dc=XXXX" filter="(&(memberuid=uid=XXXX,)(cn=*)"

A manual ldapsearch for the below does work:

ldapsearch -x -D "uid=XXXX,ou=XXX,dc=XXX" -W -H  -b "ou=XXX,dc=XXX" "(&(memberuid=XXXX)(cn=*))"

It LOOKS in the logs like Splunk is trying to do this equivalent search:

ldapsearch -x -D "uid=XXXX,ou=XXX,dc=XXX" -W -H  -b "ou=XXX,dc=XXX" "(&(memberuid=uid=XXXX,ou=XXX,dc=XXX)(cn=*))" 

Specifically, if it would just not put the DN in the filter, it should work. Any advice to get this working?

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...