I am working on gtk based UI for gSSO, It is about to ready, testing is going on.
I guess by this weekend, i can push the functional UI.
From: Kanavin, Alexander
Sent: Friday, July 12, 2013 6:57 PM
To: Ohly, Patrick
Cc: SyncEvolution; ken(a)vandine.org; Laako, Jussi; Valluri, Amarnath
Subject: Re: SyncEvolution + SSO + credentials
On 07/12/2013 05:34 PM, Patrick Ohly wrote:
> 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.
Yes, but the redirect uri is again a part of account configuration info,
provided by the app to gsso. OAuth plugin uses what it gets from the app
and doesn't hardcode the uri.
When using libaccounts-glib, where does the client key come from?
to me like SyncEvolution would still need some kind of setting for
"google-calendar" where that piece of information is stored.
libaccounts-glib is meant for public information that is not specific to
any client, so you need to store the client key inside your binary, or
read it from some secret file, or use gsso with a password plugin for
storing and retrieving the client id/key securely.
Or are you saying that libaccounts-glib would store the key/value
that I described above, including SyncEvolution's own client key?
Yes, except the SyncEvo's client id and key.
Any chance to get that fully-working example program soonish that we
talked about? :-)
I'll start working on it early next week, but we also need a functional
gtk-based gsso UI component (where the browser magic happens). Amarnath,
do you have any idea about how long it's going to take?
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.