Feature request: Support for "headless" authentication now that "OOB flow" has been blocked
bpoliakoff opened this issue · 2 comments
When I attempt to use the googledrive library on a server, and trigger an authentication with "drive_find(n_max = 25)", the library opens a new browser tab to process the oauth request, but it's blocked by Google:
Details:
The out-of-band (OOB) flow has been blocked in order to keep users secure. Follow the Out-of-Band (OOB) flow migration guide linked in the developer docs below to migrate your app to an alternative method.
Request details: redirect_uri=urn:ietf:wg:oauth:2.0:oob
[Related developer documentation](https://developers.google.com/identity/protocols/oauth2/resources/oob-migration)```
Is there any hope for migrating the authentication flow to one of the one of the alternatives spelled out on Google's "Out-Of-Band (OOB) flow Migration Guide" (https://developers.google.com/identity/protocols/oauth2/resources/oob-migration)?
The authentication flow works smoothly on a local installation of rstudio, but when running on a server, the OOB flow is triggered, and fails, due to Google's having blocked that flow.
Yes, I am well aware of this situation.
It has already been addressed by gargle 1.3.0 (which handles auth for googledrive and more), released in January.
The most recent version of googledrive requires that version of gargle, so that will force even more folks to upgrade.
If you want to read more about the history, see: