Google Drive Connector Fails When "Malware or Spam" Is Detected

[0xRy4n]

The Google Drive connector will fail if a file is detected as containing "Malware or Spam".

<HttpError 403 when requesting https://www.googleapis.com/drive/v3/files/<SNIP>?alt=media returned "This file has been identified as malware or spam and cannot be downloaded.". Details: "[{'message': 'This file has been identified as malware or spam and cannot be downloaded.', 'domain': 'global', 'reason': 'cannotDownloadAbusiveFile'}]">

This is problematic in cases where company content is likely to trigger such a warning. In my case, the content in question is content related to penetration testing as my company deals with educational cybersecurity content and labs.

This (supposedly) can be remedied by using the acknowledgeAbuse=True in the get_media() call. For example, on line 330 of google_drive/connector.py you have:

response = service.files().get_media(fileId=file["id"]).execute()

Which could be changed to:

response = service.files().get_media(fileId=file["id"], acknowledgeAbuse=True).execute()

Obviously, whether this is a behavior you want is highly circumstantial.

I am suggesting having this as a connector configuration setting. You would then wrap these calls to catch the error and recall with the acknowledgeAbuse argument if the setting to allow this is enabled.