Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Google Drive authentication randomly fails in a multi-node cloud environment

Written By

Madeleine Clay

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Google Drive authentication usually works correctly, but sometimes it randomly fails with java.lang.IllegalStateException: Authorization oAuth2State not initialized errors in the logs.
  • Google Drive was linked to the environment correctly following the official documentation.
  • My environment is clustered.

Environment

  • Quarterly Release
  • PaaS
  • SaaS

Resolution

Additional Information

  • Google Drive authentication can fail when users switch nodes between storing and retrieving credentials, because the nodes access different instances of the map storing the credentials.
  • The fix for LPD-41695 broadcasts any changes to a map storing credentials across all the nodes in a cluster.

 

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?