As part of the Neo4j continuous release process we rolled out Bloom version 2.5.0 (upgrading from Bloom version 2.4.1) on Wednesday 19th October 2022 at approximately 10:00 UTC.
Upon rolling out the new version of Bloom, Aura Enterprise customers using SSO to login to Bloom faced an error and couldn’t gain access.
All other users Free / Professional and Enterprise not relying on SSO were unaffected.
Users (Aura Enterprise only) attempting to sign-in to Bloom via SSO were faced with the login error : “Neo4j connectivity has been lost. Please check if your database instance is up and running”
Most customers could still revert to native authentication and resume work if they chose to do so.
Despite all our attempts to safeguard any existing functionality there was an issue in the implementation of the SSO login. Our normal software testing did not reveal any SSO related issue prior to release.
After some rapid investigations it was deemed not to be a configuration issue and we decided to roll-back the new version and revert to Bloom version 2.4.1 meanwhile we could correct the issue.
We are improving our pre-release testing processes to better detect this type of scenario prior to future releases. We have also taken steps to make a roll-back of versions easier and faster for our teams to perform as an extra safety.