| Issue 2377: | Private Google Calendars via OAuth | |
| 10 people starred this issue and may be notified of changes. | Back to list |
When FullCalendar used v1 of Google Calendar's API, it was able to accept a private feed URL with a "magic cookie" that one could create/revoke in the Google Calendar UI. Since being forced to move to v3 of Google's API, this is impossible. OAuth seems like the best way to go about restoring this functionality: https://developers.google.com/google-apps/calendar/auth Related to Issue 1249
Nov 25, 2014
Project Member
#1
adamrs...@gmail.com
Dec 9, 2014
We used to use fullcalendar to show events from from a private google calendar within an intranet page. Please keep this scenario into account while implementing oauth / writing the user guide; probably there is a way to use a refreshed OAuth token with a long expiration (e.g.: 1 year) so that fullcalendar works out of the box for viewers without having to force a full oauth flow to each one.
Feb 9, 2015
Issue 2413 has been merged into this issue.
Feb 9, 2015
note to self: look at Issue 2413 to investigate the demo w/ angular
Aug 21, 2015
Discussion for this issue has moved to the following URL: https://github.com/fullcalendar/fullcalendar/issues/2642 This is because Google Code is shutting down. Apologies if you are being pestered with these notifications. This is a one-time event. Happy coding, Adam
Status:
ExportedToGithub
|
|
| ► Sign in to add a comment |