Skip to main content

Magellan Release Notes

Release Notes for the Magellan HaaS Series

This release will include all fixes incorporated into previous HaaS versions. You can access our release history in the Release History page.

End of Life Notice for Magellan Series

The Magellan series has a planned End of Life (EOL) date of 28 February 2027.

To minimise interruption to services for banking and energy customers, Magellan support has been extended through to 28 February 2027. This provides banking and energy customers with six months from the Orion series release in September 2026 to plan and complete their migration. Magellan will also continue to cover the upcoming July 2026 and November 2026 FDOs, which keeps the breaking changes mandated for Nebula to a minimum.

During this period, the Nebula series is delivered as an NBL-only release. This allows newly onboarded NBL customers to align to our latest series without requiring banking and energy customers to migrate on the same time horizon. Banking and energy customers will have visibility of Nebula's breaking changes ahead of the Orion series, which is scheduled for release in September 2026 and will extend key features introduced in Nebula, including Redirect to App.

Please refer to the Nebula Release Notes for the breaking changes introduced in Nebula, and the EOL Schedule for full details on series timelines.

CDS FDOs, Data Adapter FDOs and other potentially breaking changes are flagged with a 🚨.

Magellan Updates​

Please see links below for Updates to the Magellan Series.


RC8​

  • BZ-9294/PRODUCT-871: Updated copy in the User/Principal search feature of HaaS Manager to align with the copy configured in the consent flow, instead of using generic default field names.
  • BZ-9434/PRODUCT-194: Fixed pagination on the Clients page in HaaS Manager. Previously, users were only shown the first page (since Magellan).
  • BZ-9562/PRODUCT-742: Fixed copy in the Biza Consumer Dashboard where a vulnerable user was informed that a notification would be sent to other Joint Account Holders (JAHs) even though the backend will (correctly) not send an email for the operation if submitted.
  • BZ-9682/PRODUCT-790: Fixed customer logo sizing in bespoke themes.
  • BZ-9261/PRODUCT-491: Updated copy in the Consumer Dashboard to correctly align with backend behaviour when withdrawing sharing approval (no notifications sent to other JAHs).
  • PRODUCT-916: Fixed error reporting that caused false positive monitoring alerts when PRD endpoints were called with HTTP POST.
  • PRODUCT-1000: Retry on register polling failures to be more resilient to transient ACCC Register CDN failures.
  • PRODUCT-968: Extended retry schedule for failed health checks from the operations API to reduce false positive rates of detecting adapter outages.
  • PRODUCT-916: Added SocketTimeoutExceptions to retryable exception list in the PRD adapter configuration, improving resilience when PRD adapters experience timeouts under heavy CDR traffic (with randomised backoff to spread out the retries).
  • PRODUCT-207: Fixed a HaaS Manager bug which caused false positive alerts in HaaS monitoring when security scanning tools scanned unknown pages in HaaS manager.

RC7​

  • 🚨 PRODUCT-77: Published Data Adapter spec to meet the 25Q301 FDO.
  • 🚨 PRODUCT-137: Implementation of Get Endpoint Metadata V4.
  • 🚨 PRODUCT-138: Implementation of Get Transaction Detail V2 due July 14th 2025.
  • 🚨 PRODUCT-39: Implementation of Get Product Detail V5 due July 14th 2025 (PRD Adapter must meet the 25Q301 FDO).
  • PRODUCT-185 (BZ-9430): Fixes a bug in HaaS Manager where the Set Customer Context page's Principal selection dropdown did not display Nominated Representative and Authority to Operate principals when searching by extended authentication attributes.
  • HAAS-4103: Fixes a bug in the Authorisation Service where syncing data recipient software product metadata from the ACCC register failed when the software product description exceeded 2048 characters.
  • HAAS-4154 (BZ-9025, BZ-9026): Fixes a bug in the Authorisation Service where the copy on the first page and the second page in the consent flow was inaccurate when a data holder sent OTPs to customers via both Email and SMS.
  • HAAS-4246: Fixes a bug in the Authorisation Service where the username login field cannot be used together with other extended attributes on the login page of the consent flow. This bug only affected Banking data holders.
  • HAAS-4271: Fixes a bug in the Adapter API client where the client incorrectly followed the mtls_endpoint_aliases object in OAuth2 server's discovery document and called the wrong token endpoint despite the fact that the client was not configured with mTLS.

RC6​

  • HAAS-4314 (BZ-9251): Fixes a bug in the Consumer Dashboard where the dashboard crashed and displayed a blank page after a user logged in successfully.

RC5​

  • HAAS-4320: Fixes a bug in Management API where the required OAuth2 access token scope was incorrect.

RC4​

  • HAAS-4317: Fixes a bug in banking Get Products endpoint and Get Product Detail endpoint where HaaS threw 500 Internal Server Error when:
    • Client sent both x-min-v and x-v headers in the request.
    • Prd adapter's highest supported version between x-min-v and x-v was higher than the highest supported version of HaaS.

RC3​

  • HAAS-4290: Fixes a bug in the HaaS Manager where Role-Based Access Control (RBAC) was missing and allowed unauthorized user to access certain HaaS Manager pages by entering page URL in browser address bar.

RC2​

  • HAAS-4229: Fixes a bug in the Consumer Dashboard that arrangements page crashes on load. This bug only affects 2 HaaS customers.

RC1​

Biza Platform​

  • 🚨 Platform Consolidation via the HaaS Flex Transition Plan to greatly simplify future HaaS deployments and set the foundation for future HaaS Releases to be optional where customers can choose their upgrades on their own schedule.
  • 🚨 HAAS-2538: Added in metrics collection and reporting for non-500 error responses to address the 25Q201 Data Standards Obligation for Data Holder metrics.
  • 🚨 HAAS-3241: Implementation of Get Endpoint Metadata V3 and removal of Get Endpoint Metadata V2 and Get Endpoint Metadata V1.
  • HAAS-3295 (BZ-8596): Corrected the default "Secondary User Instruction Added" SendGrid template. This fix is applicable only to customers using Biza's default SendGrid templates.
  • 🚨 HAAS-3762: Removed support for Hybrid Flow Authentication. Authorization Code Flow is now the only supported Authentication Flow see Historical Obligations.
  • Added native multi-brand support for a HaaS Space in two modes: Branded Domains (the previous multi-brand setup) and a Single Domain setup where the endpoints are all realmed. See Multi-Brand for more information.
  • HAAS-2656, HAAS-3238, HAAS-3298 (BZ-7323, BZ-8377) Security enhancements.
  • Unplanned Outages: Previously, availability metrics only reflected the status of the HaaS platform and did not account for adapter availability or unplanned outages. As part of the Flex improvements, any unplanned outages reported in HaaS Manager will now be included in the availability metrics reported to the ACCC. See here for further information.

Authorisation Service​

  • HAAS-3009 (BZ-8248): Removed the arrangement amended notification from being sent when a joint account owner withdraws sharing approval for an account in a specific arrangement. This notification is not required by the rules and only led to confusion due to the simple structure our the default SendGrid template.
  • HAAS-3185 (BZ-8406): Adjusted handling of the 404 responses from the Data Adapter listAccounts endpoint during consent flow. Instead of an error screen, consumers now see no accounts available for selection.

Data API​

  • HAAS-3170 (BZ-2104): A 503 response from AEMO is now passed through to the ADR as a 503. Previously this was passed through as a 500.

Customer Dashboard​

  • HAAS-2449 (BZ-6740): Fixed the back button functionality to navigate to the browser's previous page instead of following the URL path.
  • HAAS-2712 (BZ-6714): Updated the "Account details" page to allow navigation to the "Manage arrangements page regardless of whether the account is part of an active arrangement. Previously, navigation was only possible if the account had at least one active arrangement. This change applies only to out-of-the-box Dashboards.
  • HAAS-2738: Improved accessibility by adding appropriate aria labels to elements where necessary.
  • HAAS-2915: Spam requests to the Consumer Dashboard are now handled appropriately with a 404 rather than a 500.
  • HAAS-3055 (BZ-4657): Copy fix for one specific customised theme.
  • HAAS-2763, HAAS-3195 (BZ-7372, BZ-8474): Fixed a bug where Secondary Users could view accounts on the arrangement details page that they did not own, but had a Secondary User Instruction applied. Now, only accounts owned by the logged in Secondary User are visible on the arrangement details page. Note that arrangement object created by a Secondary User will remain visible to them, even in cases where some accounts referenced in the arrangement are no longer shared, or the where the Secondary User is not the owner. This is for continuity and historical purposes, and is expected behaviour.

Adapter API​

  • No changes

Documentation​

  • HAAS-3382, HAAS-3426, HAAS-3429: Added clarification on Private Secondary Users with regards to Data Adapter setup, notifications and Consumer Dashboard visibility.
  • HAAS-3624: Updated HaaS Administration documentation to demonstrate the new Customer Context feature of HAAS-3150.
  • Updated the FDOs page to include all known FDOs for 2025.
  • Added our latest CX Checklist results to the Consumer Experience feature page.

HaaS Configuration​

  • HAAS-2039 (BZ-6328): Allows for the customisation of the date-time formatter used in SendGrid notifications.
  • HAAS-3294 (BZ-8471): Updates to branding for one specific customer.

Management API​

  • HAAS-2658: The GrantV1 object now contains userId and principalId, which is required to understand arrangement ownership in downstream Dashboards.
  • HAAS-3780 (BZ-8883): Reduced the expiry of the JWT issued by the Dashboard SSO Request endpoint from 30 minutes to 30 seconds.

HaaS Manager​

  • 🚨 HaaS Admin has been superceded by HaaS Manager and is removed in Magellan. HaaS Manager requires Biza ID federation to be finalised before HaaS Manager can be used.
  • Initial release of HaaS Manager. See HaaS Manager for more information.
  • HAAS-2854 (BZ-7644): Renamed Customer Count to CDR Consumers (Active) on the metrics page. Also added CDR Consumers (Inactive).
  • HAAS-3150 (BZ-8291): Added functionality to perform actions with a Customer Context representing a specific user regardless of the authentication mechanism that is configured with HaaS (e.g., loginId, username, dob, mobile number etc).

PRD Admin​

  • 🚨 PRD Admin is superceded by Product Manager (for Banking PRD) and HaaS Manager (for Statuses and Outages) and is removed in Magellan.

Biza Conformance Suite​

  • No changes

Developer Portal​

  • No changes