bloom.neo4j.io potentially degraded for Aura VDC SSO users

This issue is resolved and should you still experience issues please implement the required changes as described in https://support.neo4j.com/s/article/Bloom-URI-Change-Impact-and-Remediation or contact customer support via https://support.neo4j.com/ .

Customers using Bloom hosted at bloom.neo4j.io and who have SSO configured for authentication (Aura VDC tier only) are impacted by an upgrade to the latest Bloom version, 2.16.0, released on October 7, 2024. A notice about the change was shared via Canny and email on August 20, 2024 [https://neo4j-aura.canny.io/changelog/upcoming-changes-to-bloom]. A reminder was posted on October 8, 2024 with details of impact and remediation [https://neo4j-aura.canny.io/changelog/bloom-update-possible-sso-issues].

Key Remediation:

Please refer to the knowledge article Bloom URI Change Impact and Remediation [https://support.neo4j.com/s/article/Bloom-URI-Change-Impact-and-Remediation] for details on what the change was, how it might impact you, and what to do if you are among the impacted cohort of customers.

In short, we removed the index.html on the end of the URI, and that change must be updated anywhere in your configuration that references it.

While we have received limited reports of customers experiencing this issue, we are marking bloom.neo4j.io Degraded for now to allow us to reach more potentially impacted Users.