Tickets :: [#12734] Google Caldav Access via OAuth 2.0

Summary	Google Caldav Access via OAuth 2.0
Queue	Kronolith
Queue Version	Git master
Type	Enhancement
State	Rejected
Priority	2. Medium
Owners
Requester	nimm (at) technikum-wien (dot) at
Created	10/03/2013 (4435 days ago)
Due
Updated	01/19/2016 (3597 days ago)
Assigned
Resolved	01/19/2016 (3597 days ago)
Milestone
Patch	No

01/19/2016 04:36:29 PM	Jan Schneider	Comment #3 State ⇒ Rejected	Reply to this comment
Since we use SabreDAV as the DAV client, it would need to be implemented there first.

10/03/2013 08:09:18 PM	nimm (at) technikum-wien (dot) at	Comment #2	Reply to this comment
Since Google changed their caldav API, access will only be possible via OAuth 2.0, see https://apidata.googleusercontent.com/caldav/v2/calid/events Therefore, OAuth 2.0 as authentication method for external calendars would be very useful for Kronolith. Sorry wrong url, this is the google info https://developers.google.com/google-apps/calendar/caldav/v2/guide

10/03/2013 08:07:18 PM	nimm (at) technikum-wien (dot) at	Comment #1 Priority ⇒ 2. Medium Patch ⇒ No Milestone ⇒ Queue ⇒ Kronolith Summary ⇒ Google Caldav Access via OAuth 2.0 Type ⇒ Enhancement State ⇒ New	Reply to this comment
Since Google changed their caldav API, access will only be possible via OAuth 2.0, see https://apidata.googleusercontent.com/caldav/v2/calid/events Therefore, OAuth 2.0 as authentication method for external calendars would be very useful for Kronolith.