[SOLVED] ZD Beta 2 Linux doesn't log in to my Zimbra account

[cesarcardoso]

Installing ZD Beta 2 on my system - Foresight Linux 1.4. Cleaned Beta 1 stuff and such.

Installed without a hitch. Running app. Setup to get my Zimbra mail from my server.

Got this on the setup window:

invoke malformed soap structure in reply: 324{"Code":{"Value":"soap:Sender"},"Reason":
{"Text":"authentication failed for cesar@zyakannazio.eti.br"},"Detail":{"Error":
{"Code":"account.AUTH_FAILED","Trace":"com.zimbra.cs.account.AccountServiceException$AuthFailedServiceException: 
authentication failed for cesar@zyakannazio.eti.br\nCode:account.AUTH_FAILED\n\tat 
com.zimbra.cs.account.AccountServiceException$AuthFailedServiceException.AUTH_FAILED(AccountServiceException.java:120)\n\tat 
com.zimbra.cs.account.AccountServiceException$AuthFailedServiceException.AUTH_FAILED(AccountServiceException.java:116)\n\tat 
com.zimbra.cs.account.ldap.AuthMechanism$ZimbraAuth.doAuth(AuthMechanism.java:112)\n\tat 
com.zimbra.cs.account.ldap.LdapProvisioning.verifyPasswordInternal(LdapProvisioning.java:2795)\n\tat 
com.zimbra.cs.account.ldap.LdapProvisioning.verifyPassword(LdapProvisioning.java:2768)\n\tat 
com.zimbra.cs.account.ldap.LdapProvisioning.authAccount(LdapProvisioning.java:2647)\n\tat 
com.zimbra.cs.account.ldap.LdapProvisioning.authAccount(LdapProvisioning.java:2626)\n\tat 
com.zimbra.cs.service.account.Auth.handle(Auth.java:110)\n\tat 
com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:342)\n\tat 
com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:208)\n\tat 
com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:113)\n\tat 
com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:272)\n\tat 
javax.servlet.http.HttpServlet.service(HttpServlet.java:727)\n\tat 
com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:174)\n\tat 
javax.servlet.http.HttpServlet.service(HttpServlet.java:820)\n\tat 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)\n\tat 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)\n\tat 
org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)\n\tat 
org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:148)\n\tat 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)\n\tat 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)\n\tat 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)\n\tat 
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)\n\tat 
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:716)\n\tat 
org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:406)\n\tat 
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)\n\tat 
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)\n\tat 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)\n\tat 
org.mortbay.jetty.handler.RewriteHandler.handle(RewriteHandler.java:176)\n\tat 
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)\n\tat 
org.mortbay.jetty.Server.handle(Server.java:313)\n\tat 
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)\n\tat 
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:844)\n\tat 
org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)\n\tat 
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)\n\tat 
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)\n\tat 
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)\n\tat 
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)\n","_jsns":"urn:zimbra"}},"_jsns":"urn:zimbraSoap"}, 
server: localhost

zdesktop.out:

[cesar@eca log]$ cat zdesktop.out 
0    INFO  [main] log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
1473 INFO  [main] log - jetty-6.1.5
2120 INFO  [main] log - No Transaction manager found - if your webapp requires one, please configure one.

Become stuck on setup window.

[jholder]

I'm seeing this as well. Please file a bug.

[jholder]

Bug 27045 - (5.0.2)malformed soap response in Desktop Beta 2

[knitcap]

I'm seeing the same issue as well. Thanks for filing the bug jholder.

[jholder]

Thanks guys for your patience! In the mean time, you can get the older version from here, if you are unable to upgrade your Zimbra server:
Zimbra 5.0 Demo Downloads

[mmorse]

Zimbra Desktop 0_84_build_1119 is now available for download & should contain a fix for syncing against servers older than 5.0.3

-The fix set zclient request/response protocol to Soap 1.2 to override default SoapJS which is cause backward compatibility issues with ZCS servers older than 5.0.3 including all 4.5.x servers.

[knitcap]

Originally Posted by mmorse

Zimbra Desktop 0_84_build_1119 is now available for download & should contain a fix for syncing against servers older than 5.0.3

-The fix set zclient request/response protocol to Soap 1.2 to override default SoapJS which is cause backward compatibility issues with ZCS servers older than 5.0.3 including all 4.5.x servers.

You guys are the best...many thanks for the quick turnaround on the new build!

[cesarcardoso]

Originally Posted by mmorse

Zimbra Desktop 0_84_build_1119 is now available for download & should contain a fix for syncing against servers older than 5.0.3

-The fix set zclient request/response protocol to Soap 1.2 to override default SoapJS which is cause backward compatibility issues with ZCS servers older than 5.0.3 including all 4.5.x servers.

Do you guys kill bugs while sleeping or what?

Totally awesome! Working flawlessly now. Thank you guys!