Re:Google will disable all but OAuth for IMAP, SMTP and POP ...
by booi on Friday January 19, 2024 @06:49AM
(#39054397)
and then have to reauthenticate it every 2 weeks because the refresh token seemingly expires for no reason...
Re:Google will disable all but OAuth for IMAP, SMTP and POP ...
by nunez on Friday January 19, 2024 @08:42AM
(#39055280)
The refresh token shouldn't expire.
Re:Google will disable all but OAuth for IMAP, SMTP and POP ...
by gerwim on Friday January 19, 2024 @09:19AM
(#39055726)
Maybe not for Google, but it's not part of the OAuth spec. It's perfectly valid for refresh tokens to expire.
Re:Google will disable all but OAuth for IMAP, SMTP and POP ...
by nunez on Friday January 19, 2024 @03:26PM
(#39060630)
Interesting. Many of the OAuth services I've used use non-expiring refresh tokens. Though I definitely agree; they should also have an expiry.
Re:Google will disable all but OAuth for IMAP, SMTP and POP ...
by justinc8687 on Friday January 19, 2024 @07:03AM
(#39054475)
If you set your app to "production", the refresh token works properly. Ignore the verification steps. It'll yell at you, but it'll work.
I ran into the same problem and one workspace disallows App passwords. You can simply get the OAuth token with a little python script and then use it as the password: https://github.com/google/gmail-oauth2-tools/blob/master/pyt...
(see for example https://github.com/lefcha/imapfilter/issues/186)