Re: OAUTH2 Authorisation Status

 >So the crucial thing is to get the Google project set to Production, not Testing.

That's my feeling - it doesn't sound as though Google would tolerate Testing for ever when access is clearly live.
So, can it be done?
Has anybody done it, recently?   - It may have been easier at some stage in the past!

And, in answer to your earlier point, David, I haven't yet gone through the rigmarole of setting up OAuth2, so have no Network log entries to look at.
I want to be reasonably sure that Google will still allow POP and SMTP through ClawsMail, without ongoing complaints about insecure third-party apps, and a need to go through re-authorisation all over again.
Will the upcoming refresh token code in Claws deal with this, at least on the basis of no holidays for more than 30 days?


On Sat, 02 Apr 2022 13:49:38 +0000
"David Fletcher" <[email protected]> wrote:

> The answer is here:
> https://developers.google.com/identity/protocols/oauth2#expiration
> 
> "A Google Cloud Platform project with an OAuth consent screen configured
> for an external user type and a publishing status of "Testing" is
> issued a refresh token expiring in 7 days."
> 
> So the crucial thing is to get the Google project set to Production, not
> Testing.
> _______________________________________________
> Users mailing list
> [email protected]
> https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users