[Users] Authorization error after setting up OAuth2

[Leon Fisk]

On Thu, 2 Jun 2022 15:42:59 -0400
Littlergirl <littlergirl at gmail.com> wrote:

<snip>
>Any help getting this across the finish line would be greatly appreciated.
>If I can't fix this and am stuck using Gmail in a browser from now on
>instead of in Claws Mail, I'll turn into a useless drooling husk in a dark
>corner of a room and that's a future I'd like to avoid if at all possible.

I enabled 2factor authentication for main Google login. Used a cell
phone number and Authentication app as second Auth methods. Then you
can create a new App Password which can be used just as we had been
doing with the Google login password. Has been working okay for maybe a
week now.

You can generate the 6 digit Authentication code on Linux by installing
the "oathtool" package. Example:

===
Linux 2 step verification (2FA) using oathtool

The syntax to generate totp is as follows:

oathtool -b --totp 'private_key'

Typically private_key only displayed once when you enable 2FA 
with online services such as Google/Gmail, Twitter, Facebook, 
Amazon, PayPal, Bank accounts and so on. You must keep private_key 
secrete and never share with anyone. Here is a sample session that 
creates code for my Twitter account.

$ oathtool -b --totp 'N3V3R G0nn4 G1v3 Y0u Up'

Sample outputs:

944092
===

I also put "Aegis Authenticator App" on my phone. Both of these
methods have been working okay to generate the second sign in code for
Google on the web...

A more elaborate method of using "oathtool" can be found here:

https://www.cyberciti.biz/faq/use-oathtool-linux-command-line-for-2-step-verification-2fa/

-- 
Leon
Claws 3.19.0, Debian