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

[Patrick Ohly]

On Tue, 2014-01-14 at 14:25 +0100, Helge Kraak wrote:
> When I apply as third command (no addressbook at the end of the
> command)
> 
> syncevolution --configure SSLVerifyServer=False
> --template SyncEvolution_Client --sync-property
> remoteDeviceId=ST23K3J5I4JX username=admin
> password=admin --source-property addressbook/uri=addressbook
>  sync=two-way Palm-TH55 at webdav 
> 
> the command 
> 
> syncevolution --print-config -q @webdav addressbook
> 
> RETURNS:
> 
> "[addressbook]
> backend = CardDAV
> database =
> https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/
> # databaseFormat = 
> databaseUser = admin
> databasePassword = admin"

When you show the config of addressbook for the Palm-TH55 peer, is the
"sync" property set? In other words, what do you get from:
syncevolution --print-config -q Palm-TH55 at webdav addressbook

> When I try your combined command (I have to
> include SSLVerifyServer=False again to make it work)
> 
> 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
> 
> IT RETURNS
> 
> "[INFO] addressbook: looking for databases...
> [INFO] addressbook: no database to synchronize
> [ERROR] addressbook: no database to synchronize"

I can't reproduce the problem here, using SyncEvolution 1.3.99.6 plus
(probably irrelevant) patches.

Which version of SyncEvolution are you using?

I can reproduce that the last step, adding a peer, will try to verify
databases again. But that works for me:

$ ./syncevolution --configure --daemon=no databaseUser=test databasePassword=testing calendar/database=http://localhost:8009/caldav.php/test/Test_davical_caldav_1/ todo/database=http://localhost:8009/caldav.php/test/Test_davical_caldav_1/ addressbook/database=http://localhost:8009/caldav.php/test/Test_davical_carddav_1/ calendar/backend=caldav todo/backend=caldavtodo addressbook/backend=carddav @webdav addressbook calendar todo
[INFO] addressbook: looking for databases...
[INFO] addressbook: okay
[INFO] calendar: looking for databases...
[INFO] calendar: okay
[INFO] todo: looking for databases...
[INFO] todo: okay
$ ./syncevolution --daemon=no --configure --template SyncEvolution_Client sync=two-way remoteDeviceId=PN70M9J5V7JX username=admin password=admin foo at webdav addressbook
[INFO] addressbook: looking for databases...
[INFO] addressbook: okay

So perhaps SSLVerifyServer simply doesn't get picked up in your case
where it is needed.

Can you try this:

SYNCEVOLUTION_DEBUG=1 syncevolution --configure SSLVerifyServer=False \
               --template SyncEvolution_Client \
               remoteDeviceId=PN70M9J5V7JX username=admin password=admin \
               loglevel=4 \
               sync=two-way \
               databaseUser=admin  \
               databasePassword=admin \
               backend=carddav  \
               database=https://localhost:443/sabredav/addressbookserver.php/addressbooks/admin/  \
               Palm-TH55 at webdav addressbook

It should show more information about the "[INFO] addressbook: no
database to synchronize" problem.

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