[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: debugging

To: Quanah Gibson-Mount <quanah@zimbra.com>, Craig White <CWhite@skytouchtechnology.com>, openldap-technical@openldap.org
Subject: Re: debugging
From: Howard Chu <hyc@symas.com>
Date: Wed, 13 May 2015 19:27:58 +0100
In-reply-to: <E21DBCC64A2A6C5678FFD909@[192.168.1.9]>
References: <SN1PR08MB1743E21047D602C79D5C3FA8B3DA0@SN1PR08MB1743.namprd08.prod.outlook.com> <BB409F882A9F6F3E1C5D7DE2@[192.168.1.9]> <SN1PR08MB174398248BC4AA53A1AC91BCB3D90@SN1PR08MB1743.namprd08.prod.outlook.com> <E21DBCC64A2A6C5678FFD909@[192.168.1.9]>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0 SeaMonkey/2.37a1

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/

References:
- debugging
  - From: Craig White <CWhite@skytouchtechnology.com>
- Re: debugging
  - From: Quanah Gibson-Mount <quanah@zimbra.com>
- RE: debugging
  - From: Craig White <CWhite@skytouchtechnology.com>
- RE: debugging
  - From: Quanah Gibson-Mount <quanah@zimbra.com>

Prev by Date: RE: debugging
Next by Date: Re: insert utf-8 data with c api (solved)
Index(es):
- Chronological
- Thread