https://bugs.meego.com/show_bug.cgi?id=23764 --- Comment #1 from pohly <patrick.ohly(a)intel.com&gt; 2012-03-21 14:25:05 UTC --- I've implemented the first part, using "databaseUser/Password" as credentials for the resource given by "database". That was good enough to use SyncEvolution as bridge between SyncML and CardDAV/CalDAV. No binaries yet. -------- Product: SyncEvolution Component: SyncEvolution MeeGo Release: unspecified Severity: enhancement Priority: Undecided Keywords: Status: ASSIGNED Who: patrick.ohly(a)intel.com Assigned To: syncevolution-bugs(a)meego.bugs Target Build: --- Flags: Changed: -------- https://bugs.meego.com/show_bug.cgi?id=23764 -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug.

https://bugs.meego.com/show_bug.cgi?id=23764 pohly <patrick.ohly(a)intel.com&gt; changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #2 from pohly <patrick.ohly(a)intel.com&gt; 2012-05-14 13:01:43 UTC --- SyncEvolution 1.3 will support the SyncML bridge mode. Nightly testing includes WebDAV on the server and client side (edsdav = EDS client+DAV server and davfile = DAV client+EDS server). I'm closing this issue as resolved, even though it would be nicer to also have the For documentation, see the extended README (aka man page) section: ---------------------------- CalDAV and CardDAV ================== This section explains how to use local syncing for CalDAV and CardDAV. Both protocols are based on WebDAV and are provided by the same backend. They share ``username/password/syncURL`` properties defined in their target config. The credentials must be provided if the server is password protected. The ``syncURL`` is optional if the ``username`` is an email address and the server supports auto-discovery of its CalDAV and/or CardDAV services (using DNS SRV entries, ``.well-known`` URIs, properties of the current principal, ...). Alternatively, credentials can also be set in the ``databaseUser`` and ``databasePassword`` properties of the source. The downside is that these values have to be set for each source and cannot be shared. The advantage is that, in combination with setting ``database``, such sources can be used as part of a normal SyncML server or client sync config. SyncEvolution then reads and writes data directly from the server and exchanges it via SyncML with the peer that is defined in the sync config. The ``database`` property of each source can be set to the URL of a specific *collection* (= database in WebDAV terminology). If not set, then the WebDAV backend first locates the server based on ``username`` or ``syncURL`` and then scans it for the default event resp. contact collection. This is done once in the initial synchronization. At the end of a successful synchroniation, the automatic choice is made permanent by setting the ``database`` property. **Warning:** the protocols do not uniquely identify this default collection. The backend tries to make an educated guess, but it might pick the wrong one if the server provides more than one address book or calendar. It is safer to scan for collections manually with ``--print-databases`` and then use the URL of the desired collection as value of ``database``. To scan for collections, use:: syncevolution --print-databases \ backend=<caldav or carddav> \ username=<email address or user name> \ "password=!@#ABcd1234" \ syncURL=<base URL of server, if auto-discovery is not supported> Configuration templates for Google Calendar, Yahoo Calendar and a generic CalDAV/CardDAV server are included in SyncEvolution. The Yahoo template also contains an entry for contact synchronization, but using it is not recommended due to known server-side issues. The following commands set up synchronization with a generic WebDAV server that supports CalDAV, CardDAV and auto-discovery. For Google and Yahoo, replace ``webdav`` with ``google-calendar`` resp. ``yahoo`` and remove the ``addressbook`` source when setting up the sync config. :: # configure target config syncevolution --configure \ --template webdav \ username=123456(a)example.com \ "password=!@#ABcd1234" \ target-config@webdav # configure sync config syncevolution --configure \ --template SyncEvolution_Client \ syncURL=local://@webdav \ username= \ password= \ webdav \ calendar addressbook # initial slow sync syncevolution --sync slow webdav # incremental sync syncevolution webdav Here are some alternative ways of configuring the target config:: # A) Server has one URL as starting point instead of DNS auto-discovery. syncevolution --configure \ --template webdav \ username=123456 \ "password=!@#ABcd1234" \ syncURL=http://example.com \ target-config@webdav # B) Explicitly specify collections (from server documentation or --print-databases). # The 'calendar' and 'addressbook' names are the ones expected by the sync config # above, additional sources can also be configured and/or the names can be changed. syncevolution --configure \ username=123456 \ "password=!@#ABcd1234" \ addressbook/backend=carddav \ addressbook/database=http://example.com/addressbooks/123456/ \ calendar/backend=caldav \ calendar/database=http://example.com/calendar/123456/ \ target-config@webdav \ calendar addressbook Finally, here is how the ``@webdav`` context needs to be configured so that SyncML clients or servers can be added to it:: # configure sources syncevolution --configure \ databaseUser=123456 \ "databasePassword=!@#ABcd1234" \ addressbook/backend=carddav \ addressbook/database=http://example.com/addressbooks/123456/ \ calendar/backend=caldav \ calendar/database=http://example.com/calendar/123456/ \ @webdav \ calendar addressbook # configure one peer (Memotoo in this example): syncevolution --configure \ username=654321 \ password=^749@2524 \ memotoo@webdav # sync syncevolution --sync slow memotoo@webdav ---------------------------- -------- Product: SyncEvolution Component: SyncEvolution MeeGo Release: unspecified Severity: enhancement Priority: Undecided Keywords: Status: RESOLVED Who: patrick.ohly(a)intel.com Assigned To: patrick.ohly(a)intel.com Target Build: --- Flags: Changed: Status Resolution -------- https://bugs.meego.com/show_bug.cgi?id=23764 -- Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug.