GNOME Bugzilla – Bug 653339
Add authentication API
Last modified: 2012-06-12 17:40:35 UTC
As discussed with Matthew Barnes, folks needs to support passing authentication data through to at least some of the e-d-s PersonaStores. Presumably this data will normally come from gnome-keyring, but I'm undecided about whether the gnome-keyring dependency should be in folks, or in the applications using folks. I suspect the latter, with the authentication API in folks being a thin abstraction layer around the possible authentication requests from folks' backends.
Punting bugs that won't be fixed by Folks 0.6.0.
How does this work currently for, eg, a Google contacts account in e-d-s? I thought the authentication was all done transparently behind our backs (like it is for the Telepathy PersonaStores).
(In reply to comment #2) > How does this work currently for, eg, a Google contacts account in e-d-s? If the user has GOA installed and set up for that account: Everything works fine. Otherwise, if the user has previously opened Evolution this session and authenticated the account (and e-addressbook-factory hasn't died in the meantime): Everything works fine. Otherwise, if the user has not used Evolution to authenticate the account in e-addressbook-factory: libfolks needs to authenticate it. Question which has just come to mind: What if folks is the only Tp client currently running, and the user has a Tp account which is configured to not “remember password”? Will Telepathy spawn a password dialogue itself, or will things just fail? In the latter case, we'd have to handle authentication ourselves as with EDS.
(In reply to comment #3) > (In reply to comment #2) > > How does this work currently for, eg, a Google contacts account in e-d-s? > > If the user has GOA installed and set up for that account: Everything works > fine. > Otherwise, if the user has previously opened Evolution this session and > authenticated the account (and e-addressbook-factory hasn't died in the > meantime): Everything works fine. > Otherwise, if the user has not used Evolution to authenticate the account in > e-addressbook-factory: libfolks needs to authenticate it. > > Question which has just come to mind: What if folks is the only Tp client > currently running, and the user has a Tp account which is configured to not > “remember password”? Will Telepathy spawn a password dialogue itself, or will > things just fail? In the latter case, we'd have to handle authentication > ourselves as with EDS. If Empathy is installed, empathy-auth-client should be launched by D-Bus activation. Failing that, we could handle it through Channel.Interface.SASLAuthentication: http://telepathy.freedesktop.org/spec/Channel_Interface_SASL_Authentication.html (which I'm sure empathy-auth-client is a good example of).
Evolution-data-server handles authentication for us now, so closing this bug.