GNOME Bugzilla – Bug 741922
Google Calendars support broken in Evolution Data Server 3.12 (from Evolution and California)
Last modified: 2015-01-13 00:03:28 UTC
When trying to add a Google Calendar directly from Evolution or California's UIs, after entering my google username and password, I get: Unable to retrieve calendar list: Authentification requise: <HTML> <HEAD> <TITLE>Forbidden</TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF" TEXT="#000000"> <H1>Forbidden</H1> <H2>Error 403</H2> </BODY> </HTML> (yes, I litterally get that shown in the error dialog in both applications)
I can confirm this behavior in California 0.2 under Fedora 21. Although I was able to add the google-acount in the setting without any problems.
The libgdata bug is reported at bug #664353. The California ticket is bug #740656.
Thanks for a bug report. I tried to reproduce this with evolution-data-server and evolution 3.12.9 and the calendar is added and shown properly for me. What I did precisely: a) switch to the Calendar view in evolution b) right-click Personal calendar and choose New Calendar c) select Google type d) fill a name and my email (without @gmail.com part) e) leave the calendar to the 'Default' f) save the changes y pressing the OK button g) write my password on the password prompt h) wait for few seconds, then my events are shown in evolution's UI Could you retry with the current stable version, please?
I don't know if it's latest stable, but running 3.12.9: 1. Switch to Calendar view 2. File -> New -> Calendar 3. Type: Google 4. User: enter Gmail address (w/ or w/o .gmail.com) 5. Press the "Default User Calendar" button (this is different than your step #e) 6. Enter Google password I get the error Jean-François describes in comment #1. Using the method you describe only accesses the main account's primary (default) calendar.
Thanks for the update. The 3.12.9 is the current stable version, at least till the next Monday, when there'll be the 3.12.10 release done. (In reply to comment #4) > 5. Press the "Default User Calendar" button (this is different than your step > #e) I see. There is used libgdata for it. Evolution just asks for the password [1] and then uses it to authenticate against the Google server using gdata_client_login_authorizer_authenticate_async(). If the server doesn't allow plain password logins anymore, then we've bad luck and the CalDAV interface sources lookup should be used here instead, avoiding libgdata altogether in this configuration utility. One can achieve this in a little awkward way already, by configuring a default Google calendar, then edit it and use Find Calendars button to get a list of known calendars and possibly choose a different one. It seems to me that this can be safely marked as a duplicate of bug #664353, but I'd need a confirmation from Philip first. Because if the libgdata interface can be accessed only by using OAuth, then the evolution part should be changed. By the way, I garbled my user name (unintentionally) when trying the first time, and the error was that the username or password is incorrect, the same as when I provide an incorrect password, thus I suppose the interface can be accessed with a plain password. [1] https://git.gnome.org/browse/evolution/tree/modules/cal-config-google/e-google-chooser.c#n519
(In reply to comment #5) > It seems to me that this can be safely marked as a duplicate of bug #664353, > but I'd need a confirmation from Philip first. Because if the libgdata > interface can be accessed only by using OAuth, then the evolution part should > be changed. Yup, looks like bug #664353 to me. *** This bug has been marked as a duplicate of bug 664353 ***