On Fri, 2013-07-12 at 17:00 +0300, Alexander Kanavin wrote:
On 07/12/2013 03:54 PM, Patrick Ohly wrote:
> What "redirect_uri" should be used when registering SyncEvolution?
I think Google provides some defaults when registering clients.
I was asking because it sounded like the value had to match what the
actual OAuth2 implementation then uses.
> The information above could be provided to SyncEvolution at
> a /usr/share/syncevolution/authentication/google-calendar.ini file. The
> content of that file is determined by the packager. In addition, files
> could also be searched for in
> or /etc/syncevolution/authentication. That way, a user and/or system
> admin could personalize or add services without having to recompile
Or you could also use libaccounts-glib :)
When using libaccounts-glib, where does the client key come from? Sounds
to me like SyncEvolution would still need some kind of setting for
"google-calendar" where that piece of information is stored.
Or are you saying that libaccounts-glib would store the key/value pairs
that I described above, including SyncEvolution's own client key?
> Does this all sound reasonable so far? Can someone explain how
> map to APIs and functionality in gSSO and UOA?
I think it's all quite reasonable; you should start looking at
libgsignon-glib to see specific APIs.
Any chance to get that fully-working example program soonish that we
talked about? :-)
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.