-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to obtain GDRIVE_CLIENT_SECRETS ? #24
Comments
Is it obtained through creating some google cloud project for a particular drive account? |
Any help would be appreciated😅! |
Here is the guide on how to set up the OAuth screen for Google: https://developers.google.com/workspace/guides/auth-overview |
We're also updating our repo to focus more on the oauth connector side of things so we'll have some updated documentation when that's done. |
It seems like google drive connector in sidekick web demo is not working. It takes to a 3rd party application but doesn't authenticate and says can't connect. Can you update some documentation on it as you have mentioned above on what are the steps? |
Hey @sundar7D0 we made some changes recently, you can find the most up to date docs at docs.psychic.dev. The google drive picker still works, you can go to dashboard.psychic.dev/playground to test it out. |
In the google-docs data connector, the GDRIVE_CLIENT_SECRETS is read in as environment variable but I am not sure where it's set or to what should a self-hosting user set it to?
Also, as of now, to authenticate using OAuth2, user has to click on "Advanced" and then proceed. But once when you register your google-doc OAuth access endpoint with Google (after which we needn't use the "Advanced" option), will the self-hosting users also get the same benefit but with full data privacy (which is a matter of great concern when dealing with google-drive contents)?
The text was updated successfully, but these errors were encountered: