Skip to main content

Mir Release Notes

Release Notes for the Mir HaaS Release

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

info

The Production deployment window for the Mir release is 9th - 17th September 2024.

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

Biza Platform​

  • HAAS-2442: Upgrades the Telstra API Gateway from V2 to V3 due to EOL. This change is relevant for Biza Managed OTP customers only.
  • HAAS-2312 (BZ-6568): Fixes a bug where the expired authorisations count metric was being incremented for grants with type client_credentials as well as CDR data sharing.
  • HAAS-2452 (BZ-6763): Fixes a bug where unattended Secondary Data Holder requests were reported as customer present requests.
  • 🚨 HAAS-1971 (BZ-5527, BZ-6042, BZ-6691): If the data adapter responds with a 451 - Ineligible Block from getUser when an ADR hits the token endpoint asking for a new access token, HaaS will revoke the corresponding data sharing arrangement and call the relevant ADR's revocation endpoint. This follows a change made to the "Revoking consent" standards in CDS v1.30.0. This might be a breaking change for customers whose intention for responding with 451 Ineligible Block is not for this scenario. Biza has informed the ACCC of the possible unintended side effect of this change. As such, we have put this behaviour behind a feature flag (defaulted to ON) with the ability to turn it OFF on request if the adapter implements getClosedPrincipals (or will support it prior to Nov 11 2024 - Phobos HaaS release). Please reach out to your Biza support contact if you have further concerns with this change.
  • HAAS-2146 (BZ-6258): Fixes a bug where notifications were sent with missing/empty account information. The reported scenario here was when sending DOMS request expiry notifications after the joint account had a Legal Block applied to it.

Authorisation Service Enhancements​

  • HAAS-1738 (BZ-4946): Adds a closed indicator to the Consent Flow review page. This change is relevant for one customer only.
  • BZ-4931, BZ-4758, BZ-4036: Variation work for a specific customer only.
  • HAAS-2430, HAAS-2425, HAAS-2299 (BZ-6060): Fixes the contrast of the checkboxes on the account selection step of the Consent Flow. This change is relevant for out of the box Consent Flows only.
  • HAAS-2298, HAAS-2363 (BZ-5636, BZ-6493): Adds an error page for when backend services (including data adapter calls) timeout. This gives the Consumer the option to click a button and be redirected back to the ADR with a relevant OAuth2 error code.

Data API Enhancements​

  • HAAS-334, HAAS-958: Reduces the likelihood of potentially verbose error messages being returned to the ADR client.
  • HAAS-2024: Reduces the number of data adapter calls made by detecting the case where there are no accounts in the arrangement that are enabled for data sharing. In this case, HaaS will not call the data adapter and simply respond with the empty list to the ADR client.

Customer Dashboard Enhancements​

  • HAAS-67: Adds a UI indicator to each account on the account list page for Secondary User's to know if an Instruction is present for relevant accounts. This change is relevant for out of the box Dashboards only.
  • HAAS-151: Removes the ability for a Secondary User to see accounts they have a relationship on but do not yet have a Secondary User Instruction in place. Previously, Secondary Users could see these accounts without a relevant account owner explicitly setting up the Secondary User Instruction. This meant that the Secondary User could see the basic account information but could not manage this account or set any notification preferences in relation to this account.
  • HAAS-1883 (BZ-6058): Add a disabled state to buttons while they are fetching data. This reduces the possibility of sending multiple requests to backend services.
  • HAAS-2301 (BZ-6724): Fixes an issue where joint account holders could not see each others data sharing arrangements. It should be noted that this extends existing behaviour where account owners could see arrangements created by Secondary Users with a Secondary User Instruction. The presence of an arrangement that is not created by the logged in user is seen by the "Created by someone else" text as opposed to "Created by you".
  • BZ-4931, BZ-4758, BZ-5550, BZ-5549, BZ-4036, BZ-4385, BZ-4488, BZ-4489: Variation work for a specific customer only.
  • HAAS-2426, HAAS-2427, HAAS-2428, HAAS-2429, HAAS-2431, HAAS-2432, HAAS-2425, HAAS-2299 (BZ-6060): Accessibility improvements including: provides alternative text for some images, ensures that content is available on all screen sizes, improves the contrast of the checkboxes on the notification settings page, adds an underline for all links and provides the language HTML attribute on all pages. This change is relevant for out of the box Consent Flows only.
  • HAAS-2343 (BZ-6666): Fixes some grammatical and copy issues in the Consent History page.
  • HAAS-2111 (BZ-6436): In the specific scenario where the data adapter is authoritative for vulnerability and the accountCustomers array in the listAccounts response does not return vulnerable field of true, HaaS calls the data adapter Get User endpoint for each account customer in order to determine the vulnerable status of each of them. This has now been optimised to only call the data adapter Get User endpoint for the currently logged in user as that is the only vulnerability HaaS needs to know about in this situation.

Adapter API Enhancements​

  • HAAS-2347 (BZ-6657): Centralises the polling of the getHealth data adapter endpoint to reduce traffic. Furthermore, the default timeout of this endpoint is now equal to the default timeout of all the other endpoints.
  • HAAS-2219 (BZ-5116): Deprecates the secondaryUserInstructionAction.secondaryUser.principalId field in the sendNotification request body. Customers that rely on this endpoint for notifications should no longer rely on this field because this user should be uniquely identifiable in the customer's systems by the userId alone. The principalId was previously set to the principalId of the account owner enabling or disabling the Secondary User Instruction which might have been accurate in some customer systems but was an incorrect assumption as a whole.

HaaS Configuration​

  • No changes

Management API​

  • No changes

Documentation​

  • 🚨 HAAS-2459: Added new data adapter specification v2.0.2 containing the changes from CDS v1.31.0.0.
  • 🚨 HAAS-2459: There is a CDS FDO for November 2024 to implement V4 of the List Energy Accounts endpoint. Please review the mapping rules to see if V2 of the adapter List Energy Accounts endpoint is required or if the existing V1 will suffice.
  • 🚨 HAAS-2459: There is an optional CDS FDO for September 2024 to implement V3 of the List Energy Account Billing Transactions endpoint. Biza will support this new version in Phobos (November 2024). Please review the mapping rules to see if V2 of the adapter List Energy Account Billing Transactions endpoint is required or if the existing V1 will suffice.
  • 🚨 HAAS-2036: Introduces an FDO (24Q404) for V2 of the Get Endpoint Meta endpoint. This version is required if List Energy Accounts V2 (CDS V4) and List Energy Account Billing Transactions V2 (CDS V3) is to be implemented. This version also removes adapter V0 which has been superseded since the V1 FDO of November 2023.
  • 🚨 HAAS-2036: Introduces an FDO (25Q103) for V3 of the Get Endpoint Meta endpoint. This version removes legacy behaviour in relation to the SUPPORTS_V0_VERSIONING feature flag. In V3, Biza will send a version in all request bodies and will expect a version in all response bodies. The x-haas-v header will become mandatory for all calls.
  • 🚨 HAAS-332, HAAS-955: Introduces an FDO (24Q403) to restrict all accountId's, principalId's and userId's across the entire data adapter specification to the following regular expression: ^[0-9A-Za-z .,=_-]+$. Following this change, HaaS will improve its input validation across all of its APIs in an attempt to improve security. Biza has already ensured that there are no existing values stored in Production that violate this regular expression - as such, this is a non-breaking change. However, customers may wish to apply such validation on their side to ensure that any future IDs will fail to match this pattern.

Developer Portal​

  • No changes

Admin API Enhancements​

  • No changes

PRD Admin Interface​

  • No changes

HaaS Admin​

  • HAAS-2265 (BZ-6298): On the arrangement detail page, the account IDs are displayed regardless of whether extra detail was successfully fetched from the upstream data adapter. The previous behaviour was to omit all account information which lead to some administrative confusion - especially with inactive arrangements for which the upstream data source may not have account details easily retrievable from core systems.

HaaS2Universe Customers​

  • No changes

Mock Servers​

  • No changes

DataRight Lab​

  • No changes

Biza Test Register​

  • No changes

Biza Conformance Suite​

  • No changes