You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Readme suggests to set the "authorize_using_code=True" option in the config.toml in order to login headless via OAuth OOB. This does not work anymore since Google deprecated this option for all client end of January 2023 (see: https://developers.google.com/identity/protocols/oauth2/resources/oob-migration).
As possible workaround the Readme could mention simply ssh forwarding here.
Thanks for the notice, this seems to be fixed in a new version of google-drive3 / yup_oauth2. I've done a long-overdue update of most project dependencies and just released gcsf v0.2.3. Both authentication flows (http redirect and code-based) work for me on a clean install and config.
Hello,
Currently the Readme suggests to set the "authorize_using_code=True" option in the config.toml in order to login headless via OAuth OOB. This does not work anymore since Google deprecated this option for all client end of January 2023 (see: https://developers.google.com/identity/protocols/oauth2/resources/oob-migration).
As possible workaround the Readme could mention simply ssh forwarding here.
ssh <REMOTE_USER>@<REMOTE_HOST> -L 8081:localhost:8081 -N
The text was updated successfully, but these errors were encountered: