For the complete documentation index, see llms.txt. This page is also available as Markdown.

Troubleshooting Google Workspace

Connection Errors

  • You may see some errors when you “test” a user account. Some may explain the cause – like this:

  • I had mis-typed the user’s email address – resulting in the “Invalid email or User ID” in that error text.

Error 401 Unauthorized

A 401 Unauthorised error is most likely caused the Domain Wide Delegation not being set using the Service Account’s UNIQUE ID value or its SCOPES have not been entered correctly.

Error – missing end tag

This one was due to in internal anti-malware service in the Archive system causing the JSON Token Key data that was uploaded on the Connection Panel to be altered. App Mail Archive systems should have been patched to resolve this issue. However, if you see this error then raise a support request with your archive vendor.

Tips

  • OAuth Configuration Issues: Ensure all OAuth URLs and credentials are correctly entered in both Google Cloud Console and YOUR ARCHIVE.

  • Service Account Errors: Verify that Domain-Wide Delegation is correctly set up and that the Service Account has the necessary permissions and scopes.

Additional Notes

As of September 30, 2024, Google Workspace is transitioning away from "less secure apps" and requires OAuth for all third-party integrations, including email clients and archiving solutions. This requires ensuring all configurations are up to date with OAuth 2.0 standards to maintain compliance and security in accessing Google Workspace data.

Last updated