Hi Patrick,
On Mon, Mar 9, 2015 at 1:20 PM, Patrick Ohly <[email protected]>
wrote
At loglevel=4 one would also see the actual HTTP traffic, which
contains
the real reason for the 403 error in the error response body.
Here it is: http://paste.ubuntu.com/10567263/ But I think, any of 3
reasons you provided, is the actual issue..
One possible reason is that Evolution uses GData APIs and
SyncEvolution
uses CardDAV. Those are controlled by different scopes in OAuth.
Ah, that's right. Evolution uses GData API.
I recently did the same exercise (getting SyncEvolution to work for
OAuth on Ubuntu Vivid) and only got it to work after changing the
Vivid
system files.
Could you please share how to do it (as a temporary solution)? I would
also love to use my own “client_id” & “client_secret” instead
of UOA’s.
Thanks.
_______________________________________________
SyncEvolution mailing list
[email protected]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
