All Apps and Add-ons

BUG: ldapfilter does not properly output whenCreated field.

peter_krammer
Communicator

App: SA-ldapsearch (Version 2.2.0)
There is a difference between the output of ldapsearch and ldapfilter when it comes to the whenCreated attribute.
In ldapfilter the output is not a date, but code that looks like it is supposed to format the date.
You can see it by running this query:

|ldapsearch domain=default search="(sAMAccountName=Administrator)" attrs="sAMAccountName,whenCreated"
|eval ldapsearch_whenCreated=whenCreated
|ldapfilter domain=default search="(sAMAccountName=$sAMAccountName$)" attrs="whenCreated"
|eval ldapfilter_whenCreated=whenCreated
|table sAMAccountName, ldapsearch_whenCreated, ldapfilter_whenCreated

alt text

0 Karma

marycordova
SplunkTrust
SplunkTrust

can you post screenshots of the output for both

@marycordova
0 Karma

BigCosta
Path Finder

The same problem with the whenChanged attribute

0 Karma

peter_krammer
Communicator

Yes of course.

0 Karma
Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

(view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...