Completed Checklist - Alfresco Federation Services - 3.2 - 3.2 - Ready - Alfresco - external - Alfresco/Alfresco-Federation-Services/3.2/Alfresco-Federation-Services/Configure/Connectors/Google-Drive-and-Gmail/Google-Drive-OAuth-Connector/Completed-Checklist - 2025-03-04

Alfresco Federation Services

Platform
Alfresco
Product
Alfresco Federation Services
Release
3.2
License

Ensure that you have all the following with your Google project:

  • A Google Drive API listed in your dashboard under APIs and Services.
  • If using Vision Tasks: A Cloud Vision API listed in your dashboard under APIs and Services.
  • A Web Application OAuth 2.0 Client, listed under Credentials of your project:
    • This should have an authorised redirect URI with the following format: {SIMFLOFY_SERVER}/3sixty-admin/authconn/oauthcb.
  • A filled out OAuth consent form page with:
    • The ApplicationName 3Sixty-VisionTextExtractor/1.0 if using Vision Tasks.
    • A support email to be used on the consent screen.
    • The email, profile, openid, ../auth/drive:
      • If using Vision Tasks ../auth/cloud-vision, ../auth/cloud-platform.
  • In Federation Services, a Google OAuth Connector using the secret key and ID from your credentials you created, and the token fields are now populated.

https://developers.google.com/identity/protocols/oauth2#expiration

Our app is in testing status, thus refresh token expires in 7 days and need to re-authenticate again.

Production status apps will not have refresh token expiry.

https://stackoverflow.com/questions/71777420/i-want-to-use-google-api-refresh-tokens-forever