[SyncEvolution] Setup of SyncML to WebDAV synchronization bridge: Problem with SSLVerifyServer switch in configuration command
Helge Kraak
helge at kraak.info
Tue Jan 14 04:40:12 UTC 2014
Thank you very much for your explanations, Patrick. Following your
advices I think I'm (hopefully) close to having a correct configuration.
Starting from an empty syncevolution configuration I apply the following
commands:
*### First command**###*
syncevolution --configure \
*keyring=no* *SSLVerifyServer=False* \
--template webdav
syncURL=https://localhost:443/sabredav/addressbookserver.php/ \
username=admin password=admin \
target-config at webdav
RETURNS:
[INFO] addressbook: looking for databases...
[INFO] addressbook: okay
[INFO] calendar: looking for databases...
[INFO] calendar: no database to synchronize
[INFO] memo: looking for databases...
[INFO] memo: no database to synchronize
[INFO] todo: looking for databases...
[INFO] todo: no database to synchronize
This is the expected output because on the WebDAV server I have only set
up an address book so far.
*### Second command ###*
syncevolution --configure \
databaseUser=admin \
"databasePassword=admin" \
addressbook/backend=carddav \
addressbook/database=*https://localhost:443/sabredav/addressbookserver.php/*addressbooks/admin/
\
@webdav addressbook
*### Third command ###*
/syncevolution --configure /*
keyring=no**SSLVerifyServer=False
*--template**SyncEvolution_Client/
--sync-property remoteDeviceId=/ST23K3J5I4JX/
username=admin password=admin
/ --source-property addressbook/uri=addressbook
--source-property calendar/uri=events
--source-property todo/uri=tasks
--source-property memo/uri=memo
Palm-TH55 at webdav
RETURNS:
[INFO] addressbook: looking for databases...
[INFO] addressbook: no database to synchronize
[INFO] calendar: looking for databases...
[INFO] calendar: backend failed: error code from SyncEvolution
authorization failed (remote, status 401): calendar: syncURL not
configured and username admin does not contain a domain
[INFO] memo: looking for databases...
[INFO] memo: backend failed: error code from SyncEvolution authorization
failed (remote, status 401): memo: syncURL not configured and username
admin does not contain a domain
[INFO] todo: looking for databases...
[INFO] todo: backend failed: error code from SyncEvolution authorization
failed (remote, status 401): todo: syncURL not configured and username
admin does not contain a domain
Here I'm stuck. What am I missing so that the database on at the WebDAV
server cannot be found?
Thanks.
Helge
On 1/13/14 9:11 AM, Patrick Ohly wrote:
> On Sun, 2014-01-12 at 03:55 +0100, Helge Kraak wrote:
>> Hi,
>>
>> during my journey of setting up a synchronization of a Palm Tungsten
>> TX running the Synthesis SyncML application and a SabreDAV server I
>> tried the following configuration command adapted from the
>> syncevolution manual:
>>
>> syncevolution --configure \
>>
>> SSLVerifyServer=False \
>>
>> databaseUser=admin \
>>
>> "databasePassword=admin" \
>>
>> addressbook/backend=carddav \
>>
>>
>> addressbook/database=https://localhost:443/sabredav/addressbookserver.php/ \
>>
>> calendar/backend=caldav \
>>
>>
>> calendar/database=https://localhost:443/sabredav/addressbookserver.php/ \
>>
>> @webdav \
>>
>> calendar addressbook
>>
>>
>>
>> It returns this error message:
>>
>> [ERROR 00:00:00] per-peer (unshared) properties not allowed:
>> SSLVerifyServer
>>
>> With other configuration commands not dealing with this specific
>> SyncML - WebDAV setup I can use this switch.
> Configure options are applied to what is mentioned as target of the
> configuration change. In this case, that are four things:
> 1. The @webdav context = ~/.config/syncevolution/webdav/config.ini
> 2. The calendar source in that context =
> ~/.config/syncevolution/webdav/sources/calendar/config.ini
> 3. The addressbook source in that context =
> ~/.config/syncevolution/webdav/sources/addressbook/config.ini
> 4. The global config = ~/.config/syncevolution/config.ini
>
> The last one is a somewhat unfortunate special case; only very few
> options go into it, so typically it doesn't get changed.
>
> In you case, SSLVerifyServer cannot be set in any of these places.
> Instead of silently ignoring it, you get the error. What you can do is
> set SSLVerifyServer in the sync config for the Palm. It'll be picked up
> from there by the backend.
>
> Not very intuitive, I know, and might even lead to potential conflicts
> (what if the option has some meaning there different from what the
> source expects?). I just don't have a good solution.
>
> One solution would be to have databaseSSLVerify* options which can go
> into the source configs. But that's leading to a further proliferation
> of similar options.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/syncevolution/attachments/20140114/aab9b57c/attachment.htm>
More information about the SyncEvolution
mailing list