Le lundi 16 juillet 2012 à 13:52 +0300, George Kiagiadakis a écrit :
> In kde-tp we store the account unique id ("cm/protocol/account")
> mapped directly to the password. We don't save the param-name (not
> needed, the auth channel doesn't ask for it)
Indeed, Empathy's schema is older than SASL ch
2012/7/16 Debarshi Ray :
>> What I am missing here is how all this blends with
>> gnome-online-accounts and the future kde web-accounts kcm. I'm not
>> sure how GOA works
>
> GOA is a single sign-on mechanism. When you add a new account in GOA, what it
> does is verify the credentials supplied by t
> What I am missing here is how all this blends with
> gnome-online-accounts and the future kde web-accounts kcm. I'm not
> sure how GOA works
GOA is a single sign-on mechanism. When you add a new account in GOA, what it
does is verify the credentials supplied by the user and stores it in
gnome-ke
On Mon, Jul 16, 2012 at 1:16 PM, Guillaume Desmottes
wrote:
> Hey,
>
> GNOME 3.6 is moving away [0] from gnome-keyring to libsecret.
> libsecret is a new client for the Secret Service DBus API. The Secret
> Service allows storage of passwords in a common way on the desktop.
> Supported by gnome-ke
Hey,
GNOME 3.6 is moving away [0] from gnome-keyring to libsecret.
libsecret is a new client for the Secret Service DBus API. The Secret
Service allows storage of passwords in a common way on the desktop.
Supported by gnome-keyring and ksecretservice.
Thanks to Stef we already have patch [1] port
