Google SSO might not work in LATAM/other regions
Nov 1, 13:22 UTCNov 1, 21:21 UTC
Duration
8h
Impact
Informational
Root cause
Not disclosed
Metabase, 90 days
0 incidents
Affected
Metabase Cloud Platform
Final update
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.
Timeline
- Resolved · Nov 1, 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.
- Identified · Nov 1, 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.
- Identified · Nov 1, 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.
More from Metabase
Full historyMetabase Store is unavailablelasted 1h 39mSome Metabase functionality unavailablelasted 27mCloud service provider service outage leading to service interruptionlasted 0mSome Metabase Cloud customers hosted in the EU are reporting their site is down or slownesslasted 8h 34mMetabase Store unavailablelasted 0mEU region not availablelasted 0m