Re: [Duplicity-talk] PyDrive backend cannot authenticate because it uses out-of-bound

[Massimiliano Leoni]

Hello Edgar and thanks for the quick reply!

I'm already using the latest version, 1.2.2, via its snap package.
I checked the new documentation you pointed me to but the PyDrive section is 
identical to the other one.

Anyway, I fiddled around a little bit in the Google console and set the project 
to "testing" [instead of "production"] so that it probably doesn't have to be 
perfectly secure and now it seems to work.

Thanks for the help!
Massimiliano


On Dienstag, 2. Mai 2023 14:13:48 CEST edgar.soldin--- via Duplicity-talk 
wrote:
> hey Massimiliano,
> 
> On 01.05.2023 19:43, Massimiliano Leoni via Duplicity-talk wrote:
> > Hello everyone,
> > 
> > I tried running duplicity to backup to my google drive and google is not
> > letting me, saying that my application is blocked because it uses
> > Out-of-bound [OOB] authentication, which is not secure.
> > 
> > In particular, I'm getting
> > 
> > Error 400: invalid_request
> > 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
> 
> what is your duplicity version? did you try the latest/greatest version
> 1.2.2?
> > and the migration guide is
> > https://developers.google.com/identity/protocols/
> > oauth2/resources/oob-migration .
> > 
> > My account is configured as a "regular account" following the instructions
> > at https://duplicity.nongnu.org/vers8/duplicity.1.html#sect26
> 
> that man page is outdated, but unfortunately we cannot delete it anymore.
> nongnu is broken.
> 
> use these ones instead
>   https://duplicity.us/docs.html
> 
> > Is there a way around this?
> 
> i actually do not see any "oob" in the current backend source
>  
> https://gitlab.com/duplicity/duplicity/-/blob/main/duplicity/backends/gdriv
> ebackend.py so my guess is, that using a current duplicity will resolve your
> issue.
> 
> good luck ..ede/duply.net
> 
> _______________________________________________
> Duplicity-talk mailing list
> Duplicity-talk@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk