On Tue, 2018-07-17 at 11:41 +0100, Pete Biggs wrote:
> It might be that OAuth2 is persisting because that's what has been
> discovered Evo should use.
Hi,
that's particularly right. Some Google services are available only when
using OAuth2, like its Tasks and Contacts. There cannot be used
password authentication for those services. Calendar (the CalDAV
interface) can work with password, but the code forces OAuth2, because
the password authentication will be dropped by Google sooner or later
anyway, just as it had been for the Contacts. Using password
authentication makes it harder with two-factor authentication too, thus
it's only better to use OAuth2.
Japhering, you already received a reference to the bug with a fix to
properly parse the OAuth2 authentication response from the Google
server "in this thread" [1] (if I'm not mistaken, in which case it was
other recent thread here), which means once your distribution provides
you an almost month old release with that fix included you'll be able
to use OAuth2 as had been intended (not talking that a newer release
had been done yesterday, the 3.28.4 version).
Bye,
Milan
[1] https://bugzilla.gnome.org/show_bug.cgi?id=795997
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
