On Mon, 2015-03-09 at 14:36 +0500, Khurshid Alam wrote: > Hi Patrick, > > On Mon, Mar 9, 2015 at 1:20 PM, Patrick Ohly <[email protected]> > wrote > > 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.
I edited /usr/share/accounts/services/google-contacts.service such that it uses a different, longer key (= different client_id and client_secret) and added 'https://www.googleapis.com/auth/carddav' to the list of scopes. I also removed all other Google services, but that was just because I didn't need them. The resulting service works for both calendar and contacts, despite the name, because 'https://www.googleapis.com/auth/calendar' was already listed. This is useful when using the service in a target-config shared by multiple datastores with both calendar and contact access. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
