Google Cloud Service Health

Google Cloud Service Health
Incidents
Security Assertion Markup Language (SAML) authentication workflows not present for some customers

This page provides status information on the services that are part of Google Cloud. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit https://cloud.google.com/.

Available
Service information
Service disruption
Service outage

Incident affecting Apigee

Security Assertion Markup Language (SAML) authentication workflows not present for some customers

Incident began at 2023-02-08 06:01 and ended at 2023-02-08 12:25 (all times are US/Pacific).

Previously affected location(s)

Taiwan (asia-east1)Hong Kong (asia-east2)Tokyo (asia-northeast1)Osaka (asia-northeast2)Seoul (asia-northeast3)Mumbai (asia-south1)Delhi (asia-south2)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Melbourne (australia-southeast2)Warsaw (europe-central2)Finland (europe-north1)Madrid (europe-southwest1)Belgium (europe-west1)London (europe-west2)Frankfurt (europe-west3)Netherlands (europe-west4)Zurich (europe-west6)Milan (europe-west8)Paris (europe-west9)Tel Aviv (me-west1)Montréal (northamerica-northeast1)Toronto (northamerica-northeast2)São Paulo (southamerica-east1)Santiago (southamerica-west1)Iowa (us-central1)South Carolina (us-east1)Northern Virginia (us-east4)Columbus (us-east5)Dallas (us-south1)Oregon (us-west1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)

Date	Time	Description
8 Feb 2023	12:25 PST	The issue with Apigee has been resolved for all affected projects as of Wednesday, 2023-02-08 12:25 US/Pacific. We thank you for your patience while we worked on resolving the issue.
8 Feb 2023	11:05 PST	Summary: Security Assertion Markup Language (SAML) authentication workflows not present for some customers Description: The 'Validation of protocol message signature failed' errors observed on Portal SAML login should be mitigated and we're still investigating an issue where the SAML login button is not available. We do not have an ETA for full resolution at this point. We will provide an update by Wednesday, 2023-02-08 13:15 US/Pacific with current details. Diagnosis: Some users are unable to login with SAML on Apigee Portals and SAML login button does not appear on the login page for some users. Users may also see the error message "Metadata issuer for https://sts.windows.net/xxx/ wasn't found" or "Validation of protocol message signature failed" when attempting an SAML login. Workaround: None at this time.
8 Feb 2023	10:41 PST	Summary: Security Assertion Markup Language (SAML) authentication workflows not present for some customers Description: The 'Validation of protocol message signature failed' errors observed on Portal SAML login should be mitigated and we're still investigating an issue where the SAML login button is not available. We do not have an ETA for full resolution at this point. We will provide an update by Wednesday, 2023-02-08 13:00 US/Pacific with current details. Diagnosis: Some users are unable to login with SAML on Apigee Portals and SAML login button does not appear on the login page for some users. Users may also see the error message "Metadata issuer for https://sts.windows.net/xxx/ wasn't found" or "Validation of protocol message signature failed" when attempting an SAML login. Workaround: None at this time.
8 Feb 2023	09:42 PST	Summary: Security Assertion Markup Language (SAML) authentication workflows not present for some customers Description: The 'Validation of protocol message signature failed' errors observed on Portal SAML login should be mitigated and we're still investigating an issue where the SAML login button is not available. We do not have an ETA for full resolution at this point. We will provide an update by Wednesday, 2023-02-08 11:00 US/Pacific with current details. Diagnosis: Some users are unable to login with SAML on Apigee Portals and SAML login button does not appear on the login page for some users. Users may also see the error message "Metadata issuer for https://sts.windows.net/xxx/ wasn't found" or "Validation of protocol message signature failed" when attempting an SAML login. Workaround: None at this time.
8 Feb 2023	09:35 PST	Summary: Security Assertion Markup Language (SAML) authentication workflows not present for some customers Description: The 'Validation of protocol message signature failed' errors observed on SAML login to Edge should be mitigated and we're still investigating an issue where the SAML login button is not available. We do not have an ETA for full resolution at this point. We will provide an update by Wednesday, 2023-02-08 11:00 US/Pacific with current details. Diagnosis: Some users are unable to login with SAML on Edge and Apigee Portals and SAML login button does not appear on the login page for some users. Users may also see the error message "Metadata issuer for https://sts.windows.net/xxx/ wasn't found" or "Validation of protocol message signature failed" when attempting an SAML login. Workaround: None at this time.
8 Feb 2023	09:03 PST	Summary: Security Assertion Markup Language (SAML) authentication workflows not present for some customers Description: Mitigation work is currently underway by our engineering team. Steps have been taken to reduce the impact of the issue in us-east1 and eu-west1 by our engineering team. We do not have an ETA for full mitigation at this point. We will provide more information by Wednesday, 2023-02-08 10:30 US/Pacific. Diagnosis: Some users are unable to login with SAML on Edge and Apigee Portals and SAML login button does not appear on the login page for some users. Users may also see the error message "Metadata issuer for https://sts.windows.net/xxx/ wasn't found" or "Validation of protocol message signature failed" when attempting an SAML login. Workaround: None at this time.
8 Feb 2023	08:29 PST	Summary: Security Assertion Markup Language (SAML) authentication workflows not present for some customers Description: Mitigation work is currently underway by our engineering team. Steps have been taken to reduce the impact of the issue in us-east1 and eu-west1 by our engineering team. We do not have an ETA for full mitigation at this point. We will provide more information by Wednesday, 2023-02-08 09:30 US/Pacific. Diagnosis: Some users are unable to login with SAML on Edge and Apigee Portals and SAML login button does not appear on the login page for some users. Users may also see the error message "Metadata issuer for https://sts.windows.net/xxx/ wasn't found" or "Validation of protocol message signature failed" when attempting an SAML login. Workaround: None at this time.

All times are US/Pacific