GNOME Bugzilla – Bug 687578
Allow OAuth / OAuth2 based providers to offer password based authentication
Last modified: 2012-11-05 21:34:53 UTC
Some providers (basically Google) do not support OAuth / OAuth2 tokens for all its different services. eg., the only way to use Google Calendars over CalDAV (which is what evolution-data-server uses) is to use password based authentication. This has a negative effect on the UX because the user is prompted for her password again after creating her account (see bug 686804). We have had similar problems in the past with GTalk and GMail where one of them supported OAuth2 and the other OAuth1. Even though GMail has now migrated to OAuth2, we do not know when Google will support OAuth2 for its CalDAV endpoint. Lets offer a workaround instead of spoiling the user experience indefinitely.
FYI, the GOA module in EDS is already set up to use GoaPasswordBased if available for *any* account type. So I don't think any EDS changes are necessary to support this. It should just start working immediately.
Created attachment 228050 [details] [review] oauth2: Allow providers to optionally offer a PasswordBased interface
Created attachment 228051 [details] [review] google: Offer a PasswordBased interface
Created attachment 228055 [details] [review] oauth2: Allow providers to optionally offer a PasswordBased interface
Created attachment 228056 [details] [review] oauth: Allow providers to optionally offer a PasswordBased interface
(In reply to comment #1) > FYI, the GOA module in EDS is already set up to use GoaPasswordBased if > available for *any* account type. So I don't think any EDS changes are > necessary to support this. It should just start working immediately. Yes, indeed, it works for me.
Committed to master. Introduces a new string (an error message), so will seek permission for freeze break before pushing to gnome-3-6.