Re: [Fetchmail-users] KeyError: 'refresh_token' error in fetchmail-oauth2

[Robert H. <rjh...@gm...>]

The Google documentation indicates that the following apps do not need
verification.  The documentation for setting this up is very well
hidden.  I've not found it yet.  The hint that I found is to follow
the "Advanced" on the consent screen
(https://support.google.com/cloud/answer/7454865#unverified-app-screen).
Unfortunately, just that hint, not further documentation.

------------- from
https://support.google.com/cloud/answer/9110914#ver-prep&zippy=%2Csteps-to-prepare-for-verification%2Cwhat-app-types-are-not-applicable-for-verification

What app types are not applicable for verification?

You do not need to submit your app for review if it's going to be used
in any of the following scenarios:

Personal Use: The app is not shared with anyone else or will be used
by fewer than 100 users. Hence, you can continue using the app by
bypassing the unverified app warning during sign-in.

SMTP/IMAP/WP: The app is used to send emails through WordPress, or
similar single account SMTP plug-ins.

Internal Use: An app is internal when the people in your domains only
use it internally. Learn more about public and internal applications.
Learn how to mark your app as internal in the FAQ How can I mark my
app as internal-only?

Domain-Wide Install: If your app is intended for only Google Workspace
enterprise users, access will depend on permission being granted by
the domain administrator. Google Workspace domain administrators are
the only ones that can whitelist the app for use within their domains.
To learn how to make your app Domain-Wide Install, see My application
has users with enterprise accounts from another Google Workspace
Domain. How does this apply to my Google Workspace or Cloud Identity
enterprise accounts?

Development/Testing/Staging: If your app is in
development/testing/staging mode and not ready to be publicly
accessible, then you do not need to submit your app for verification.
Note that your app will be subject to the unverified app screen and
the 100-user cap will be in effect when an app is in
development/testing/staging. If your app is for
Development/Testing/Staging, it is recommended that you keep your
app’s publish status set to Testing and only update to In Production
once it is ready for public use. If your app’s publishing status is
set to “Testing” and not “In production”, then you do not need to
submit your app for verification. Note that your app will be subject
to the unverified app screen and the 100-user cap will be in effect
when an app is in development/testing/staging. Learn more about
Publishing status.

Service Accounts: When your app is trying to access data from users'
Google Cloud project and can run API requests on its behalf. To
understand what service accounts are, see Service accounts. For
instructions on using a service account, see Using OAuth 2.0 for
Server to Server Applications.


-- 
Robert Horn
rjh...@gm...