Companies / Metabase Cloud / incidents

Metabase Cloud: Google SSO might not work in LATAM/other regions

Affected components: Metabase Cloud Platform

Timeline of updates

1. identified2022-11-01 13:22 UTC

   On Oct-31th, Google pushed a change without notice to their oAuth2 flows to the LATAM and other regions changing the name of a parameter that broke all SSO flows. We're actively working to push a new version of Metabase with a hotfix along upgrading our Cloud instances. In the meantime, please use username/password authentication if you cannot authenticate to your Metabase instance.

2. identified2022-11-01 19:40 UTC

   We finished the release process to obtain a new Metabase version that includes the fix for the issue. We'll be starting our Cloud upgrade process in the next hour.

3. resolved2022-11-01 21:21 UTC

   We have started rolling out 44.6 version which includes the fix for the SSO issue. All instances should be upgraded in the next few hours.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Metabase Cloud profile · Recent Metabase Cloud incidents · Markdown · JSON