3 ms·

Shouldn't be _too_ hard to convert your scripts. I ran into the same problem and one workspace disallows App passwords. You can simply get the OAuth token with

Shouldn't be _too_ hard to convert your scripts. 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/python/oauth2.py https://github.com/google/gmail-oauth2-tools/blob/master/pyt... (see for example https://github.com/lefcha/imapfilter/issues/186 https://github.com/lefcha/imapfilter/issues/186)

booi 3y ago
and then have to reauthenticate it every 2 weeks because the refresh token seemingly expires for no reason...
- justinc8687 3y ago
  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.
  - xmprt 3y ago
    How can you set an app to production without Google verification if you're not in a workspace. I'm guessing the answer is that there is no way.
- nunez 3y ago
  The refresh token shouldn't expire.
  - gerwim 3y ago
    Maybe not for Google, but it's not part of the OAuth spec. It's perfectly valid for refresh tokens to expire.
    - nunez 3y ago
      Interesting. Many of the OAuth services I've used use non-expiring refresh tokens. Though I definitely agree; they should also have an expiry.