Results 1 to 5 of 5

Thread: Problem configuring GAL (Autocomplete)

  1. #1
    Join Date
    Oct 2007
    Posts
    4
    Rep Power
    8

    Default Problem configuring GAL (Autocomplete)

    I'm trying to set up autocomplete using external LDAP lookup, and I dont' want to use the GAL Sync. I've verified my filters and server config is correct but keep getting this error when I try my query test.

    And my config keeps turning the gal sync, how do I disable this completely?

    Code:
    GAL mode: External
    Server type: LDAP
    LDAP filter:(|(cn=%s*)(sn=%s*)(givenName=%s*)(mail=%s*))
    Autocomplete filter:(|(cn=%s*)(sn=%s*)(givenName=%s*)(mail=%s*))
    LDAP search base: ou=people,dc=xxx,dc=xxx
    Here is the error I get:

    Code:
    soap:Receiver
    system failure: unable to search gal
    com.zimbra.common.service.ServiceException: system failure: unable to search gal
    ExceptionId:btpool0-17://zimbratst01.dhcp.xxx.com:7071/service/admin/soap/CheckGalConfigRequest:1281396580464:988a54611c80417c
    Code:service.FAILURE
    	at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)
    	at com.zimbra.cs.account.ldap.LdapUtil.searchGal(LdapUtil.java:754)
    	at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal(LdapUtil.java:850)
    	at com.zimbra.cs.account.ldap.LdapUtil.searchLdapGal(LdapUtil.java:835)
    	at com.zimbra.cs.account.ldap.Check.checkGalConfig(Check.java:204)
    	at com.zimbra.cs.service.admin.CheckGalConfig.handle(CheckGalConfig.java:62)
    	at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:420)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:274)
    	at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158)
    	at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:291)
    	at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:212)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    	at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:181)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
    	at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    	at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
    	at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:132)
    	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
    	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
    	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
    	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
    	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
    	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.handler.DebugHandler.handle(DebugHandler.java:77)
    	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    	at org.mortbay.jetty.Server.handle(Server.java:326)
    	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:543)
    	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939)
    	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
    	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
    	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
    	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
    	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
    Caused by: javax.naming.OperationNotSupportedException: [LDAP: error code 12 - The server is not configured to pass through control 1.2.840.113556.1.4.319]; remaining name 'ou=people,dc=xxx,dc=xxx'
    	at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3101)
    	at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2987)
    	at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2794)
    	at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1826)
    	at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1749)
    	at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:368)
    	at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:338)
    	at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:257)
    	at com.zimbra.cs.account.ldap.ZimbraLdapContext.searchDir(ZimbraLdapContext.java:663)
    	at com.zimbra.cs.account.ldap.LdapUtil.searchGal(LdapUtil.java:708)
    	... 39 more
    Can someone tell me what I'm doing wrong?

  2. #2
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    25

    Default

    Welcome to the forums

    What external LDAP software are you running ? Just searching for "The server is not configured to pass through control" on any engine appears to provide quite a few hits.

  3. #3
    Join Date
    Oct 2007
    Posts
    4
    Rep Power
    8

    Default

    Hi uxbod,

    Thanks, I was looking at that on Google too. We're using Sun Directory Server v6.3 here. I'm not sure what control is the problem though. I had autocomplete working a long time ago with Zimbra 4.5 and searching through the forums it looks like it was revamped with 6.0.

    I have a suspicion it may be related to LDAP paging. Sun uses VLV, but we don't support it (currently). I have tried limiting the search results, and making sure the gal sync is turned off. Although every time I go back into the GAL config it is turned back on. Is this correct?

    I have also tried setting zimbraGalLdapPageSize to 0, which should disable paging. But I still get the error...

    Any thoughts?

    *edit* - I should note that external LDAP authentication to the same server works fine.

  4. #4
    Join Date
    Oct 2007
    Posts
    4
    Rep Power
    8

    Default

    Hmmmm, I may have been going down the wrong path regarding paging.

    I have it turned on in my dev environment and still get the error. Unless its an issue specifically with VLV, which is different than simple paged results.

    I can't think of anything else that would be a problem....

  5. #5
    Join Date
    Oct 2007
    Posts
    4
    Rep Power
    8

    Default

    okay, looks like I was on the right track.

    I tried this command and got this response -

    Code:
    ldapsearch -h ldap-it.xxx.com -b dc=xxx,dc=com -E pr=10 -x "cn=teststring"
    
    # extended LDIF
    #
    # LDAPv3
    # base <dc=xxx,dc=com> with scope subtree
    # filter: cn=teststring
    # requesting: ALL
    # with pagedResults control: size=10
    #
    
    # search result
    search: 2
    result: 12 Critical extension is unavailable
    text: The server is not configured to pass through control 1.2.840.113556.1.4
     .319
    So, I know simple paged results isn't supported by Sun LDAP and it looks like this is what Zimbra is attempting to do.

    According to 5.0.11 Directory Schema - Zimbra :: Wiki, setting zimbraGalLdapPageSize to 0 should disable paging, but it doesn't seem to be the case.

    I tried both of these commands and restarting Zimbra:

    Code:
    zmprov md xxx.com zimbraGalSyncLdapPageSize 0
    zmprov md xxx.com zimbraGalLdapPageSize 0
    Any way to disable paging completely or have support for VLV?

    Thanks

Similar Threads

  1. Replies: 5
    Last Post: 07-27-2010, 05:49 AM
  2. Yet another strange/buggy GAL behavior
    By Carello in forum Zimbra Connector for Outlook
    Replies: 3
    Last Post: 10-13-2009, 03:33 AM
  3. Replies: 1
    Last Post: 05-28-2008, 05:18 AM
  4. [SOLVED] Upgraded to 5.0 OSS - Sendmail Problem
    By Chewie71 in forum Installation
    Replies: 11
    Last Post: 12-28-2007, 07:07 PM
  5. problem while configuring sleepycat
    By ravinder in forum Developers
    Replies: 1
    Last Post: 04-13-2006, 05:18 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •