We've captured commonly asked questions about the recent change that Google has introduced around Google Identity Services. If you can't find what you are looking for, feel free to contact us.

• Google is discontinuing the Google Sign-In JavaScript Platform Library for web which is currently used in Connector for Google Drive & Confluence.

• By default, newly created Google Cloud Platform client IDs are now blocked from using the older Platform Library, whereas, existing client IDs are unaffected.

• ServiceRocket is working to replace the deprecated Platform Library with the new Google Identity Services (GIS) library to allow you to continue using Connector for Google Drive & Confluence without any interruptions.

Frequently Asked Questions

Is the Connector for Google Drive and Confluence affected by this change?

ServiceRocket’s Connector for Google Drive and Confluence uses some auth modules that are affected by this deprecation and removal. According to the announcements, new clients will stop supporting these modules starting from the 30th of April 2022.

The development team is actively working on supporting all of the breaking changes and the next major version of the plugin will have complete support for the new GIS library and modules.

How does this affect my pages with the Drive macro?

As long as you continue using the same GCP client you had before the 30th of April 2022, the app and macros should continue to function as they always have been with no issues or interruptions. Google will continue to allow this until the 31st of March 2023. Learn more.

What if I need to set up a new GCP client?

You can upgrade to version 2.6.14 which has a backward compatibility flag that will continue to be supported by Google until the 29th of July 2022.

What is the timeline for this change?

The new major version of the connector is tentatively expected to be released by mid June 2022.

What are the expected changes to the app?

The app will now manage access and refresh tokens for users to be able to access their drive files and folders. Initial tokens will be obtained after getting consent via signing in through Google. Then, the tokens will be seamlessly renewed when needed. Additionally, the drive file (legacy) macro will be removed.

Will my user experience be any different?

The user experience should remain largely unchanged. You will, however, need to give the client consent again for every Google account to be used.

Related articles

1. Discontinuing Google Sign-In JavaScript Platform Library for web

2. Discontinuing authorization support for the Google Sign-In JavaScript Platform Library

3. Google Sign-In JavaScript client reference  |  Google Sign-In for Websites  |  Google Developers