Currently, I am in the process of developing a Google App Engine application where users can fill out an online form. Depending on how the form is filled out, a calendar event is created in a specific Google Calendar. My concern lies with the authorization aspect of this project - I want the form to be completely accessible to the public without requiring any sort of login to create the calendar event.
I have managed to successfully implement the form and post creation using OAuth2, but only when I am signed in.
Here's what I have set up:
- An app registered as form-app(.appspot.com)
- A Google account identified as form-app-admin(@gmail.com) which owns the Google Calendar receiving the posts
- An API Project managed by form-app-admin
I have utilized these components along with the google-api-python-client library (including its oauth2decorator), following the example provided for Google App Engine. When logged in as form-app-admin and visiting form-app.appspot.com, everything functions as intended. However, if not signed in as form-app-admin, the functionality breaks down.
My goal is to grant the permission to write events to form-app-admin's primary calendar directly to the application itself, rather than relying on the user currently interacting with the app. Is there a better approach to achieving this? The key requirement is that anyone, whether logged into Gmail or not, should be able to complete the form and generate a calendar event.
If anyone has the necessary Python code to make this work, I would greatly appreciate it. But more importantly, I am seeking guidance on how to navigate this issue, given my limited experience with authentication-related tasks.
Thank you for your time! /Tottish