Gmail OAuth/OOB deprecation: how to fix?

[lilydjwg]

On Thu, May 05, 2022 at 09:51:32PM +0100, Dave Ewart wrote:
> [...]
>
> They refer to
> https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html
> 
>     "What do I need to do?
> 
>     "Migrate your app(s) to an appropriate alternative method by
> following these instructions [... as per the instructions in the blog
> post above ...]:"
> 
> Then they list my 'apps', which is something I just called
> 'mutt-gmail-auth' in my GSuite account.
> 
> Being quite honest, I don't really understand what it's describing here
> as I don't understand OAuth - I just followed a HOWTO! Nor can I see
> what to do to fix it. I don't understand what OOB means in this context.
> Does the config just need a minor tweak, or is this whole approach a
> complete non-starter now that Google has changed stuff?

If you are using it in testing mode, you don't need to do anything as
they say:

> No action is required on your part as apps using OOB in testing mode
> will not be affected by this change.

The OOB refers to you manually copy the access code from your browser to
your application.

Without OOB, you can run a local web server or register your own
protocol to receive the code.

-- 
Best regards,
lilydjwg