LDAP-310: Log LDAP queries generated by spring-ldap

[spring-projects-issues]

Jose Martinez (Migrated from LDAP-310) said:

I would be useful for the debugging purposes to have log the final query string sent to the server as well as the parameters. Something we can copy-paste into the LDAP server and see how it runs. Similar to the way JdbcTemplate shows the queries and parameters executing a query.

I'm creating this Jira as per the following StackOverflow post: https://stackoverflow.com/questions/24061834/how-to-see-the-query-generated-by-spring-ldaptemplate.

[StevenByks]

I was trying to figure out how to turn on extra logging, and came across that exact SO post, which lead me here. Debug logging would be so incredibly useful.

[kkrawczy]

+1, I also find it useful to see ldap queries.

[gael-ft]

+1

[nunoc]

+1

[hanusto]

+1

[chupetoide]

+1

[kutis96]

+1

[erdbeerschnitzel]

+2 :)

[rwinch]

Does someone want to create a PR for this?

[ggauravag]

+1

[naorbar]

Rob, I'll take a look... Naor

[mastermind3043-zz]

+1

[tofuatjava]

+1

[lafferty-common]

+1

[khafizovar]

+1

[KrashLeviathan]

+1 Has this really been an open issue for 8 years?

One workaround for manual searches is to log the Filter returned by LdapQuery.filter().

LdapQuery query = query().where("someAttribute").is("some value")
    .and(query().where("objectClass").not().is("unwanted"));
log.debug("LDAP query: " + query.filter());
List<?> results = repository.findAll(query);

...logs...

LDAP query: (&(someAttribute=some value)(!(objectClass=unwanted)))

[ranma2913]

+1 again. Having trouble understanding the ldap query behavior when comparing what ApacheDirectoryStudio returns vs. Spring-Data-LDAP.