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

- Impact (vendor’s label): none
- Status: resolved
- Started: 2022-11-01 13:22 UTC · Resolved: 2022-11-01 21:21 UTC · Duration: 8.0 h
- Updates: 3 · Affected components: Metabase Cloud Platform
- [Vendor status page: https://stspg.io/3hbfwmgqj3vg](https://stspg.io/3hbfwmgqj3vg)
- [Company: Metabase](https://rewindex.com/company/metabase.md)

## Timeline of updates

- **identified** 2022-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.
- **identified** 2022-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.
- **resolved** 2022-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.


---
Canonical: https://rewindex.com/company/metabase/incidents/mgqrhyr959gr · Markdown: https://rewindex.com/company/metabase/incidents/mgqrhyr959gr.md · JSON: https://rewindex.com/api/v1/companies/metabase/incidents/mgqrhyr959gr · Generated 2026-10-18T12:23:08.254Z