All Apps and Add-ons

Getting error when using ldapsearch command, even with an admin account.

3DGjos
Communicator

Hello,

I'm working with some ldapsearch queries in my environment, but I have the following problem. Even if I execute the command from an admin account it says this:

External search command 'ldaptestconnection' returned error code 1. Script output = "error_message= # host: xxx.xx.xx.1: Could not access the directory service at ldaps://xxx.xx.xx.x:636: password is mandatory in simple bind "

Then I tried installing the ldapsearch add-on in my QA environment, and the connection test passed the first time, but the second one didn't. And when I execute any ldapsearch command queries the error is the same:

External search command 'ldaptestconnection' returned error code 1. Script output = "error_message= # host: xxx.xx.xx.1: Could not access the directory service at ldaps://xxx.xx.xx.x:636: password is mandatory in simple bind "

Even using an admin system role can delete role account with all the required capabilities.

Thanks in advance!

0 Karma
1 Solution

3DGjos
Communicator

I managed to solved it. My solution: just re-enter the password for the AD account user you are using to read the groups in the domain in the interface. and it magically worked.

View solution in original post

0 Karma

3DGjos
Communicator

I managed to solved it. My solution: just re-enter the password for the AD account user you are using to read the groups in the domain in the interface. and it magically worked.

0 Karma
Get Updates on the Splunk Community!

Enterprise Security (ES) Essentials 8.3 is Now GA — Smarter Detections, Faster ...

As of today, Enterprise Security (ES) Essentials 8.3 is now generally available, helping SOC teams simplify ...

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...