Skip to main content
Solved

Gmail OAuth2 Token Expiration – Not Appearing in Refresh Application Access Tokens Screen


Denham
Jr Varsity III
Forum|alt.badge.img

Hello everyone,

I'm encountering an issue while setting up a Gmail account using OAuth2 authentication in Acumatica.

I’ve followed the instructions provided in the official wiki/help article to configure everything correctly on both Google Cloud and within Acumatica. Everything appears to be working initially — I’m able to authenticate using the “Sign In” button under External Applications or Email Accounts, and outgoing emails are sent successfully.

However, the problem is that the authentication only persists for about 8 hours. After that, the connection expires, and the account is no longer authorized to send emails. From what I understand, this is expected behavior with OAuth2 — the access token should be refreshed periodically.

The issue is that the Gmail account/application does not appear on the Refresh Application Access Tokens screen in Acumatica. As a result, we’re unable to set up automatic token refresh, which means we have to manually re-authenticate every 8 hours.

Has anyone else experienced this or found a way to resolve it? I’d like to avoid using the less secure App Password option, especially since it's deprecated and may be removed by Google at any time.

I’ve attached screenshots showing the External Application configuration and the empty Refresh Token screen.

Thanks in advance for any guidance or suggestions!

 

Best answer by Denham

Wound up getting it working somehow. I already had a separate project set up for just this use within Google cloud. I signed in and it just so happened to start working by automatically refreshing the token, without me having to set up an automation schedule on the refresh tokens screen within Acumatica.

View original
Did this topic help you find an answer to your question?

4 replies

darylbowman
Captain II
Forum|alt.badge.img+13

Forum|alt.badge.img

@Denham You should create a separate project in Google for each of your tenants and configure them individually in Acumatica.


Denham
Jr Varsity III
Forum|alt.badge.img
  • Author
  • 31 replies
  • April 16, 2025

@darylbowman ​@ranjithduraisamy72 

Thank you for your replies. I have already done this by creating a new project in google cloud for the tenant. I’m still getting the same results. I only have 1 email so far, that I am trying to set up using OAuth.

I am happy to provide screenshots of the google cloud side of things if necessary.


Denham
Jr Varsity III
Forum|alt.badge.img
  • Author
  • 31 replies
  • Answer
  • April 21, 2025

Wound up getting it working somehow. I already had a separate project set up for just this use within Google cloud. I signed in and it just so happened to start working by automatically refreshing the token, without me having to set up an automation schedule on the refresh tokens screen within Acumatica.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings