The certificate error has been fixed (not exactly sure why, but it works).
The environment I'm using is:
- Zimbra 6.1
- Funambol 8
- ZimbraConnector as posted in this thread by zoltan67
I've changed Funambol to use the jre from Zimbra to solve the class version problem.
I'm trying to test sync using the Funambol Java Demo Client. The log file includes the following lines:
Code:
LOAD ZimbraConnector 0.5.02
Source URI: scard
Last stored anchor '1255087859545' is different from the current anchor sent by the client '0'. A slow sync will be forced.
This is followed by some XML containing SyncML tags and some more log statements including the following lines:
Code:
fjg-utr+YFYN2Jj4C9omSQQTjw==/mathew@example.com: synchronization ending
Database 'scard' in state CONFIGURED
Database 'scal' in state CONFIGURED
SyncStrategy synchronization completed.
fjg-utr+YFYN2Jj4C9omSQQTjw==/mathew@example.com: synchronization completed
moving to state STATE_ERROR
Logging out...
moving to state STATE_ENDED
The full log is attached to this post.
In the zimbra mailbox.log I did notice these lines appear shortly after the sync request completed.
Code:
2009-10-09 22:20:10,015 INFO [btpool0-193] [ip=127.0.0.1;] soap - AuthRequest
2009-10-09 22:20:10,172 INFO [btpool0-193] [name=zimbra;ip=127.0.0.1;] soap - GetAllServersRequest
At the same time these lines appeared in audit.log. Looking at logins from Zimba Desktop, I would ahve expected to the account to be
mathew@example.com Code:
2009-10-09 22:20:10,015 INFO [btpool0-193] [name=zimbra;ip=127.0.0.1;] security - cmd=AdminAuth; account=zimbra;
2009-10-09 22:20:10,015 INFO [btpool0-193] [name=zimbra;ip=127.0.0.1;] security - cmd=Auth; account=zimbra; protocol=soap;
I've checked out a copy of the connector source, so I'm happy to get my hands dirty but I would appreciate some pointers in the right direction.