- This topic has 1 reply, 2 voices, and was last updated 1 hour, 34 minutes ago by
.
Just received an email from Google about breaking changes to the Google Picker API. If I understand correctly, this change will break your Google Browser cloud storage plugin. I wanted to be sure you are aware of the change, and verify that the plugin will continue to be supported.
I’ll paste the contents of the email below.
Thanks!
—
We are strengthening the Google Picker API’s authorization model to provide the highest level of data protection. This requires an update to OAuth parameters and migration for native desktop or mobile apps.
Dear developer and/or administrator,
You are receiving this communication because your organization manages applications that integrate with the Google Picker API using sensitive or restricted Google Drive OAuth scopes.
We are proactively enhancing the security of the file selection process to provide stronger protection for user data, by migrating to a new Google Picker API for mobile and desktop applications. This change will be enforced in 60 days, starting November 16, 2026.
We have provided additional information below on the impact of this change on your organization.
What this means for your organization
Google Workspace is introducing updated security and authorization requirements for all Google Picker API integrations:
Browser-based authorization: The standard Google Picker API will operate exclusively within external web browsers rather than embedded webviews
Native application display: Developers must implement changes in the code as native desktop and mobile applications are required to use the new OAuth API to be able to access Google Picker from the app
Mandatory OAuth parameters: Developers must include two new parameters in their OAuth authorization requests for the drive.file scope:
prompt=consent
trigger_onepick=true
Streamlined customization: You can now configure file selection limits (single/multiple files) and MIME type restrictions directly within the OAuth request parameters
Enforcement deadline:
There is a 60-day grace period. The new requirements will be strictly enforced after November 16, 2026, and older authorization flows will be blocked.
Impact of non-compliance after the deadline:
Functionality blockage: Third-party applications that continue to use the original Google Picker API in embedded webviews will fail to authorize, resulting in blocked file selection functionality
Workflow interruption: Applications that do not update to the new Google Picker API will also be blocked from using the Picker API
What you need to do
Action required:
If your application integrates the Google Picker API with a native desktop or mobile app, complete the following steps before November 16, 2026:
Update browser handling: Configure your implementation to launch the Google Picker API exclusively in an external web browser, not an embedded webview
Update OAuth parameters: Modify your OAuth authorization requests for the drive.file scope to include the new required parameters: prompt=consent and trigger_onepick=true
Deploy application updates: Release and distribute the updated app versions to your users before the enforcement date
We are here to help
We understand this change may require changes to your integration. If you have questions, or require additional help, please refer to our documentation on Overview of desktop and mobile apps or contact Google Workspace Support (Issue Number: 553524326).
Thanks for choosing Google Workspace.
– The Google Workspace Team
Hi @Brad,
Thanks for flagging this and for sharing the details of the announcement.
Yes, we are aware of the upcoming changes to the Google Picker API and the November 16 enforcement deadline. We will review the required changes and take the necessary actions to ensure our Google Cloud Storage integration remains compatible and supported.
Thanks again for bringing this to our attention.
You must be logged in to reply to this topic.