13 May
2015
13 May
'15
11:27 a.m.
Quanah Gibson-Mount wrote:
--On Wednesday, May 13, 2015 6:24 PM +0000 Craig White CWhite@skytouchtechnology.com wrote:
The above log line clearly indicates the client issued a search using a base of cn=accesslog. This would be a bug in the java code. ---- Thanks - that was valuable. Despite all configuration to JNDI which says where to search, the application is choosing to search 'cn=accesslog' - that was we needed to know.
Using JNDI for LDAP is a very, very bad idea.
I'd strongly advise you point your Java LDAP devs at the Unbound ID SDK for Java.
Or the Apache LDAP SDK for Java. Or OpenLDAP's JLDAP. Anything but JNDI.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/