Re: [Evolution] More authentication headaches

[Milan Crha <mcrha redhat com>]

On Sun, 2016-10-09 at 23:44 +0100, Pete Biggs wrote:
> OK, I've just installed it and it looks OK so far - at least for the
> last 10 minutes or so!

        Hi,
just a note, 10 minutes is not enough.

The problem begins after the OAuth2 token expires. The tokens are given
for 60 minutes usually (currently in the Google case). It "seemed to
work" from the evolution start, because for example the Mail part
refreshed the token and the other parts (calendars/tasks/contacts)
picked the refreshed token. After the refresh interval (the Calendar
setting, which also defaults to 1 hour) the token is expired and the
CalDAV would try with the expired token, but the evolution-data-server
code chose to not include authentication header at all, which the
Google server doesn't like and it adds to the limit, which results in
the "Exceeded Limit" after some time. Currently, after the latest
changes, the CalDAV refreshes the token before even trying to talk to
the server. The Tasks and Contacts can work slightly differently, as
they use libgdata instead, with a custom OAuth2 authorizer, but what I
tried looked fine (not that it didn't when I've been testing the
earlier changes locally).
        Bye,
        Milan