From helge at kraak.info Thu Sep 18 23:48:08 2014 From: helge at kraak.info (Helge Kraak) Date: Fri, 19 Sep 2014 01:48:08 +0200 Subject: [SyncEvolution] Setup of SyncML to WebDAV synchronization bridge: Problem with SSLVerifyServer switch in configuration command In-Reply-To: <1408524695.31890.16.camel@pohly-mobl1.fritz.box> References: <1389600679.5855.404.camel@pohly-mobl1.fritz.box> <52D4BEF3.4080101@kraak.info> <1389684576.19530.7.camel@pohly-mobl1.fritz.box> <52D522EE.6040606@kraak.info> <1389702191.19530.15.camel@pohly-mobl1.fritz.box> <7B7F85B6-A897-4F94-853D-AD321B6A685F@kraak.info> <1408369669.6141.65.camel@pohly-mobl1.fritz.box> <24A114CA-9511-4403-953F-C36D02023028@kraak.info> <1408524695.31890.16.camel@pohly-mobl1.fritz.box> Message-ID: Hello Patrick, sorry for my late update on this. The good news is that I managed to get a working configuration in the meanwhile. Your hint about adjusting the uri was correct. In addition the only remaining problem was the discovery of the addressbook by the syncevolution config process. I figured out that the database url was the problem. Instead of "database=https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/ [1]" I had to use "database=https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/addressbook" [1] to get the sync finally working. Unfortunately I don't have the testserver set up anymore so that I can't give more detailed debug information at the moment in case you would maybe want to further investigate the syncevolution behavior. But once I set it up again for my live system I will let you know in case I'm facing the same issue again. I will probably use the Baikal server variant instead of the pure sabredav server variant so possibly the issue may not reappear in case the Baikal configuration for the sabredav server is different. I'd like to express my appreciation again for your kind assistance. I'm very much looking forward to have a live system running soon which allows me to have a modern custom, transparent and reliable PIM organisation for probably at least the next 5 to 10 years. After realizing that the Palm PIM organisation which I used for more than 10 years wouldn't fit into my expectations of efficient and reliable organisation anymore in the future it took me three years to draft and evaluate a new concept (of course I only had limited time to work on it). I'm so glad that I finally found a convincing solution in which syncevolution will play an important role, especially for the contacts part. Thanks again. Helge Am 2014-08-20 10:51, schrieb Patrick Ohly: > On Wed, 2014-08-20 at 00:53 +0200, Helge Kraak wrote: > >> Am 18.08.2014 um 15:47 schrieb Patrick Ohly: > On Mon, 2014-08-18 at 15:02 +0200, Helge Kraak wrote: [...] > syncevolution --configure SSLVerifyServer=False --template SyncEvolution_Client remoteDeviceId=PN70M9J5V7JX username=admin password=admin sync=two-way databaseUser=admin databasePassword=admin backend=carddav database=https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/ [1] Palm-TH55 at webdav addressbook [...] >> Does this lead to a configuring that your phone can use? > In my Synthesis SyncML client I get the error message: DB not found (404). Synthesis does not use "addressbook" as uri by default, as far as I remember. Try editing your Synthesis SyncML client settings and enter "addressbook" as uri for contacts. Alternatively, you can also add "uri = contacts" to the configure line above to set that as alias for the the "addressbook" source. > Maybe important: Instead of "database=https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/ [1]" I used "database=http://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/ [2] " for the config this time as I also didn't use https in the SyncML client (the SSL connection for the Syncevolution server doesn't work yet in my test server setup but the SSL for the Sabredav server works already). The client always was set up for no SSL connection before so it was a potential mistake to set up the syncevolution server with SSL database link. SSL for SyncML and SSL for WebDAV are conceptually independent (*). It's okay to use it for one and not the other. (*) The only caveat is that the SSLVerifyServer=False property applies to both, for practical reasons. > ########### FOLLOWING YOUR ADVICES FROM YOUR EMAIL FROM JANUARY 22, 2014 I REPEATED THE COMMAND ABOVE WITH ADJUSTED DATABASE SETTINGS: 1. VARIANT: https://localhost:443/sabredav/addressbookserver.php/addressbooks/ [3] INSTEAD OF https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/ [1] syncevolution --configure SSLVerifyServer=False --template SyncEvolution_Client remoteDeviceId=PN70M9J5V7JX username=admin password=admin sync=two-way databaseUser=admin databasePassword=admin backend=carddav database=https://localhost:443/sabredav/addressbookserver.php/addressbooks/ [3] Palm-TH55 at webdav addressbook RETURNS "[INFO] addressbook: looking for databases... [INFO] addressbook: start database search at https://localhost:443/sabredav/addressbookserver.php/addressbooks/ [3], from sync config 'palm-th55 at webdav', source config 'addressbook', database='https://localhost:443/sabredav/addressbookserver.php/addressbooks/ [3]' [INFO] addressbook: okay" [...] >> This looks wrong. I doubt that the parent collection really is an address book collection. Thanks for the database scan output. It shows that both start URLs lead to the same collection, https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/default/ [4] That means that the variant where that URL is used for "database" is the correct one. The second one is incorrect and should have been rejected by SyncEvolution. The code checks that it can find a contact collection using the given database URL, but later SyncEvolution will use the URL as-is and then fail. The initial check must test the given URL instead of searching for databases. I will fix that. In general, the advice for setting up CardDAV/CalDAV is to first configure username/password/syncURL in a target-config. Then either don't specify "database" properties at all (and rely on SyncEvolution to pick the default ones automatically) or to use --print-databases to find the right ones (if not known already). See https://syncevolution.org/documentation/syncevolution-usage#caldav-and-carddav [5] Links: ------ [1] https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/ [2] http://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/ [3] https://localhost:443/sabredav/addressbookserver.php/addressbooks/ [4] https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/default/ [5] https://syncevolution.org/documentation/syncevolution-usage#caldav-and-carddav -------------- next part -------------- An HTML attachment was scrubbed... URL: From patrick.ohly at intel.com Fri Sep 19 06:02:21 2014 From: patrick.ohly at intel.com (Patrick Ohly) Date: Fri, 19 Sep 2014 08:02:21 +0200 Subject: [SyncEvolution] Setup of SyncML to WebDAV synchronization bridge: Problem with SSLVerifyServer switch in configuration command In-Reply-To: References: <1389600679.5855.404.camel@pohly-mobl1.fritz.box> <52D4BEF3.4080101@kraak.info> <1389684576.19530.7.camel@pohly-mobl1.fritz.box> <52D522EE.6040606@kraak.info> <1389702191.19530.15.camel@pohly-mobl1.fritz.box> <7B7F85B6-A897-4F94-853D-AD321B6A685F@kraak.info> <1408369669.6141.65.camel@pohly-mobl1.fritz.box> <24A114CA-9511-4403-953F-C36D02023028@kraak.info> <1408524695.31890.16.camel@pohly-mobl1.fritz.box> Message-ID: <1411106541.23662.186.camel@pohly-mobl1.fritz.box> On Fri, 2014-09-19 at 01:48 +0200, Helge Kraak wrote: > Unfortunately I don't have the testserver set up anymore so that I > can't give more detailed debug information at the moment in case you > would maybe want to further investigate the syncevolution behavior. It would have been nice to get confirmation that the 1.4.99.4 indeed works better with SabreDAV. It should, because I revised database discovery and error checking. But don't worry, if it doesn't, someone will find that out sooner or later. > I'd like to express my appreciation again for your kind assistance. You're welcome. -- 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.