Closed Bug 910793 Opened 11 years ago Closed 11 years ago

Remote Google Calendar (OAuth2) fails to edit/add events (Error 403)

Categories

(Calendar :: Provider: CalDAV, defect)

x86_64
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: gNeandr, Unassigned)

Details

Setup a calendar at Lightning with sync to a Google Calendar (OAuth2) works with downloading events stored on the GCal. 
Any change at the Goggle Calendar will be shown at LG after sync.
But any change at LG to an existing event or adding an event with LG will produce an Error 403.

See error log at
https://dl.dropboxusercontent.com/u/35444930/LG_GCal2_test/LG%26GCalV2_ERROR403%282013-08-29.txt

Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Thunderbird/25.0a2
Lightning 2.7a2
It's about 
{username}@googlemail.com vs {username}@gmail.com! And it seems it's only with OAuth2 with Google!

Remember there was a specific situation (legal disput) over here in Germany with the address ending '@gmail.com'.
So Google had to change for German users to '@googlemail.com'. 
Nowadays also in Germany you can use the shorter form.

If the Google account was initialized with {username}@googlemail.com you can define a LG calendar with {username}@gmail.com and it will download the events. But any edit/add will produce Error 403!
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
This seem to cause some trouble for German users, please consider adding a note to the release notes, wiki, FAQ, or wherever the OAuth2 feature will be described.
I've added this to the release notes etherpad and will also mention in the blog post. I'm a little behind on those things.
You need to log in before you can comment on or make changes to this bug.