GAL/LDAP fails every time with 5.0 RC2

[jefferai]

I have a new install of Open Source edition being used to try Zimbra out. We have an established LDAP server here that works great with Thunderbird, etc., but I keep getting weird problems trying to set up GAL to use external LDAP as a source. One of two things always happens. Keep in mind that:

$ ldapsearch -x -h someserver -b "OU=People,O=Someplace,C=US" "(someField=*something*)"

always works perfectly well.

In Zimbra, if I set up the default autocomplete filter, the correct search base (same as the ldapsearch query), and make my filter something reasonably easy, like (using the same values as the ldapsearch above): (someField=*%s*)

then I input something in for %s and Test, the test returns successfully, with no entries shown in the box -- and Finish, Next, and Back are all greyed out, so my only options at that point are Help and Cancel.

Now, if I make my filter something more complex, like:

(&(|(cn=*%s*)(sn=*%s*)(gn=*%s*)(mail=*%s*)))

then I always get a Java exception:

javax.naming.NamingException: [LDAP: error code 80 - NDS error: remote failure (-635)]; remaining name 'ou=People,o=Someplace,c=US'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.jav a:3049)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCt x.java:2951)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCt x.java:2758)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1 812)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:17 35)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_sea rch(ComponentDirContext.java:368)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContex t.search(PartialCompositeDirContext.java:338)
at javax.naming.directory.InitialDirContext.search(In itialDirContext.java:257)
at com.zimbra.cs.account.ldap.LdapUtil.searchDir(Ldap Util.java:1122)
at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal( LdapUtil.java:898)
at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal( LdapUtil.java:878)
at com.zimbra.cs.account.ldap.Check.checkGalConfig(Ch eck.java:183)
at com.zimbra.cs.service.admin.CheckGalConfig.handle( CheckGalConfig.java:50)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:345)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:212)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:117)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:272)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:174)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:405)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)

What is going on here?

[jefferai]

If I go to my Zimbra box, and go to /opt/zimbra/openldap/bin and run:

./ldapsearch -x -h somehost -b "OU=People,O=Someplace,C=US" "(cn=*Jeff*)"

Then it works perfectly well. So it's not an obvious problem with openldap on the Zimbra box.

Running CentOS 5 (using RHEL 5 Zimbra distribution).

[jefferai]

I'm bumping this. Zimbra is installed as a trial that I can hopefully demo to our higher-ups, but this is going to be a no-go if I can't integrate it with our existing contacts LDAP database.

[jefferai]

Bump. Bump.

[quanah]

What's your external directory server? Does it show any connection from the Zimbra server? Any errors?