[SyncEvolution] Setup of SyncML to WebDAV synchronization bridge: Problem with SSLVerifyServer switch in configuration command

[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/  \
> > >              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/"
> I used
> "database=http://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/ " 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/ 
> > > INSTEAD OF 
> > > https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/ 
> > > 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/  \
> > >              Palm-TH55 at webdav addressbook
> > > 
> > > RETURNS
> > > 
> > > "[INFO] addressbook: looking for databases...
> > > [INFO] addressbook: start database search at
> > > https://localhost:443/sabredav/addressbookserver.php/addressbooks/,
> > > from sync config 'palm-th55 at webdav', source config 'addressbook',
> > > database='https://localhost:443/sabredav/addressbookserver.php/addressbooks/'
> > > [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/ 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

-- 
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.