[Resending and extending my original reply from July 10th - I only
noticed now that Sunny had BCCed the mailing list]
On Thu, 2013-07-11 at 01:09 +0530, Sunny wrote:
Google made caldav & carddav api public again ( http://goo.gl/8i81d
& changed their calendar api-end point from
But new api-end point doesn't work with basic http authentication. And
old end-point will stop working after 16 September, 2013.
I tried with following command:
SYNCEVOLUTION_DEBUG=1 syncevolution --print-items --daemon=no \
It failed with " HTTP 401 Unauthorized" response code as mentioned in
Here is the log ( http://paste.ubuntu.com/5862621/
That's expected - SyncEvolution and its underlying DAV library, neon, do
not know how to use the new authentication mechanism.
I am currently documenting a Ubuntu-wiki for syncevolution
method documented there will not work after 16 sept.
Hence the obvious question: Will next release of Syncevolution support
Yes, that's the highest priority item on my list of things to do for the
upstream 1.4 release. I consider lack of that feature a release blocker.
My current thinking is that I'll reuse the work done by different
single-sign-on (SSO) services for authenticating against Google. That
will be easier than trying to replicate that work and give a better user
experience (integration into the system's credential and account
handling) - if there is such a system.
The downside will be that getting SyncEvolution up and running with
Google without such a system will be impossible, unless someone from the
community adds the code for a builtin authentication backend.
More specifically, I intend to lay the foundation for plugable SSO
backends and make it work in combination with gSSO
). That is something that I can justify as part of
my work on Tizen.
Some developers from Ubuntu expressed an interest to make it work with
Ubuntu Online Accounts, which has a very similar API.
[ fast forward to September ]
The current status is that I am one full test run away from including
OAuth2 support in the master branch. That test should be complete after
the weekend. A 18.104.22.168 beta release could follow middle of next week.
This whole work got delayed a bit because it got mixed up with fixing
FDO #66110 ("GTK-UI + D-Bus: password not stored in GNOME keyring or
). Sorry for
As originally planned, gSSO is one way of doing OAuth2. I have also
added support for GNOME Online Accounts. However, only GNOME Online
Accounts >= 3.10 (in freeze, not released yet) will have support for
). CalDAV is
already possible since 3.8. There is a hacky way to add CardDAV to 3.8
binaries - see attached README.
Ubuntu Online Accounts is not supported at the moment; I'm still hoping
to get patches for that.
Overall it'll be harder to users to get a working setup. Thus my
question to users: how much do you depend on CalDAV and/or CardDAV sync
with Google? On which platforms?
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.