Google Drive Plugin No Longer Working.(2022/02)

[VladTepz 46]

With changes to the Google API, they no longer allow you to pass "&access_token=<ACCESS TOKEN>" as a query parameter.
It needs to have the access token in the request header instead of the query parameter.

The plugin currently uses this URL scheme to pass the URL to clients, which results in a "Server returned 403 Forbidden (access denied)" error in the logs.

https://www.googleapis.com/drive/v2/files/<FILE ID>?alt=media&source=downloadUrl&access_token=<ACCESS TOKEN>

-----

Quote

download calls to files.get, revisions.get and files.export endpoints which authenticate using the access token in the query parameter will no longer be supported.

Only requests that download media content (alt=media) are affected by this change.

The access token should be provided in the HTTP header, like Authorization: Bearer oauth2-token or, if that's not possible, follow the workarounds provided in the referenced documentation:

For file downloads, redirect to the webContentLink which will instruct the browser to download the content. If the application wants to display the file to the user, they can simply redirect to the alternateLink in v2 or webViewLink in v3.

For file exports, redirect to the export link in exportLinks with the desired mime type which will instruct the browser to download the content.

-----

These Examples work fine.

Curl Example:

curl \
  -H "Authorization: Bearer [Access Token]" \
  'https://www.googleapis.com/drive/v3/files/[File ID]?supportsAllDrives=true&alt=media'

API Key Example:
(Although using just an API key requires the file to be shared in order to work)

https://www.googleapis.com/drive/v3/files/<FILE ID>?key=<API KEY>&alt=media

-----

Reference:
 - Changes in authorization to Google Drive API
 - Authorization via HTTP header
 - v2 files get documentation
 - v3 files get documentation

-----

Hopefully this is something that can be looked into.

[VladTepz 46]

Just to follow up.

The media will fallback to normal playback, after a small, added delay, from it failing. 
Not sure if many people will notice the plugin being broken, unless they are paying attention. 

Unfortunately, this makes the plugin useless, & should probably be removed/depreciated from the Plugins Catalog if there is no suitable fix. 

[Luke 37049]

Thanks for the report. We're looking into what our options are. Thanks.