All Apps and Add-ons

User permissions:Why are ldapfilter, ldapgroups, ldapfetch not working with non-default stanza?

schose
Builder

Hi forum,

I'm trying to setup sa-ldapsearch for multiple clients. The whole idea is that a client is not allowed to use lookups of another client while using the same searchhead. I tried to copy SA-ldapsearch and rename the app in app.conf to give application level permissions. Every ldap app has its own ldap.conf, which look like this..

[bwtest.loc]
alternatedomain = BWTEST
basedn = DC=bwtest,DC=loc
binddn = svc-splunk@bwtest.loc
port = 389
server = 192.168.208.10
ssl = 0

command ldapsearch is working fine, but ldapfilter, ldapgroup and ldapfetch is not:

2018-09-11 15:42:57,500, Level=ERROR, Pid=19384, File=configuration.py, Line=407, Missing required value for alternatedomain in ldap/BWTEST.
2018-09-11 15:52:11,294, Level=ERROR, Pid=19892, File=configuration.py, Line=407, Missing required value for alternatedomain in ldap/bwtest.loc.

it looks like configuration.py is not finding the alternatedomain in bwtest.loc stanza. if i configure the settings in the default stanza, it works for me - unfortunately, this does not work for multiple concurrent installations.

any hints? Has anyone installed multiple instances of SA-ldapsearch on a single search head?

Regards,
Andreas

0 Karma
Get Updates on the Splunk Community!

Streamline Data Ingestion With Deployment Server Essentials

REGISTER NOW!Every day the list of sources Admins are responsible for gets bigger and bigger, often making the ...

Remediate Threats Faster and Simplify Investigations With Splunk Enterprise Security ...

REGISTER NOW!Join us for a Tech Talk around our latest release of Splunk Enterprise Security 7.2! We’ll walk ...

Introduction to Splunk AI

WATCH NOWHow are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. ...