On Tue, 2013-03-12 at 17:53 +0100, Sean M. Pappalardo wrote:
Hello.
I've been looking for a lightweight solution to allow SyncML clients to
talk to my (SOGo) CalDAV/CardDAV server and found SyncEvolution and its
recently-added bridge capability. (I have been trying to use Funambol
but since finding SyncEvo much lighter weight and without unneeded
additional parts, I want to try getting it working.)
My first question: is it possible for SyncEvolution to pass to the DAV
server the username and password the SyncML client uses to authenticate?
SOGo needs them to show available resources for that user. If so, how?
No, that's not supported. Do you want the SyncEvolution SyncML server to
be used without any per-user configuration? In other words, tell it to
act as bridge and then let it be used automatically by different users?
That's not what it was designed for. It's more like a "personal SyncML
server" where each user configures and runs is own instance of it. Even
adding new devices of that one user has to be done manually.
If not, can that capability be added?
It could be done, but would require quite a bit of work for defining how
to automate the necessary config steps and implementing that.
My second issue is with actually setting SyncEvo up as a bridge since
I'm totally new to it. Lacking a step-by-step list on your HOWTO page
(!),
You are welcome to contribute that. In the meantime, have a look at the
recent email exchange with Christof - he went through the same process.
this is what I've done so far after piecing together the
relevant
documentation:
1) Running Debian Stable/Squeeze, I installed the syncevolution-bundle
package from your Debian repo (Thank you for providing this!)
2) Installed missing prerequisite packages for syncevo-http-server:
python-dbus python-twisted-web python-gobject python-openssl
(You probably want to update your package's 'depends' list to include these)
The -bundle does intentionally not depend on everything that is needed.
It's a bit hacky, but I'd rather not force other users to install
something that they don't need.
3) Tested running the server with:
syncevo-http-server --start-dbus-session
http://localhost:9000/
4) Tried having my Nokia S40-based phone do a sync (via an Apache
reverse proxy,) but got:
[ERROR] syncevo-dbus-server: /org/syncevolution/Server: message type
'application/vnd.syncml+wbxml; charset=UTF-8' not supported for starting
a sync
(Searching the Web for that error resulted in a message you sent in 2011
saying something to the effect of it should be supported.) So I figured
I'd better try and configure SyncEvolution. :) So I did:
Yes, that's a bit strange. You should see a message about a missing
config for this client and then be able to create that config, as
described here:
https://syncevolution.org/wiki/http-server-howto
5) syncevolution --configure --template webdav preventSlowSync=0
syncURL=https://myserver.mydomain.com/SOGo/dav target-config@myservicename
...and I got four "okay" messages
At this point you need to also set databaseUser, databasePassword and
database for the "calendar" and "addressbook" source in the
@myservicename context.
6) syncevolution --configure --template SyncEvolution_Client
syncURL=local://@myservicename username=- password=- myservicename
calendar addressbook
This is probably from the instructions for setting up a local sync.
That's not needed for acting as a SyncML bridge. Instead have a look at
the README and how it configures a SyncML client inside the
@myservicename context, using the "calendar" and "addressbook" source
configured there earlier.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.