Find answers from the community

Updated 2 years ago

Is anyone using the google drive reader

At a glance

The community member is using the Google Drive Reader API in their workflow, where a user authenticates with Google, and the community member stores the access and refresh tokens. The issue they are facing is that the Google Drive Reader launches its own callback process, waiting for OAuth callbacks, which means the API is launching web pages instead of just processing the data.

In the comments, another community member suggests handling the Google authentication outside of the Google Reader. The original community member responds that they have already done that and fixed the issue by manually creating the creds.txt file that the PyDrive library needs, though they describe it as a "bit hacky".

Another community member asks if the original community member found a solution, as they are looking to do something similar with Quickbooks. The original community member says they have not found a real solution yet, and that the issue seems to be with their implementation of the Google OAuth libraries. They mention that they can work around it by creating a new credentials.txt file for each subsequent call to the API, but they describe it as a "mess".

There is no explicitly marked answer in the comments.

Is anyone using the google drive reader in an API?

My workflow is:
  • User auths with google and I store their access_token and refresh token
  • User sends some folder_ids over to the API
  • I refresh credentials using the refresh token if necessary
  • GoogleDriveReader attempts to download and index the documents
My problem with this process is that the google drive reader launches it's own callback process, waiting for OAuth callbacks... This means my API is launching web pages rather than just processing the data.
b
H
S
4 comments
Sounds like you might want to handle google auth outside of the google reader
I've already done that. I've fixed it by manually creating the creds.txt that pydrive needs... bit hacky but it works
@HABBYMAN did you wind up finding a solution for this usecase? I'm looking to do something similar with Quickbooks at the moment, looking for examples of the clientside oauth for REST-based tools used in webapps.
No real solution in sight ATM. I think it comes down to my implementation of Google's oauth libraries though. You can get around it by creating new credentials.txt for each subsequent call to the API, but it's a mess
Add a reply
Sign up and join the conversation on Discord