Release 1.7.3

Release in prep for the Q1 2022 deployment

CustomerInfo
Manual Registration fix

Release 1.7.2

Contains a fix for Manual Client Registration.

We expect the TPP's browser to be configured to use an OBWac to connect to the register endpoint. The OBWac and SSA used in the UI must belong to the same Open Banking Directory organisation.

#483

Release 1.7.1

Fixes the /user/data api issues;
This api now supports true MATLS in that you must provide a Bearer access token when using the /data/user apis.
The user is identified from the obri-session cookie in the request, while the Bearer Access Token is used to ensure that the TPP making the request is onboarded. The access_token must have been issued to an OpenID client that belongs to the same organisation as the MATLS OBWac certificate used to create the TLS connection over with the request is sent.
The apis now create/delete Customer Info etc.
So, this completes ForgeCloud/ob-deploy#815
And contains the full fix for ForgeCloud/ob-deploy#831

Release 1.7.0

Description

• Final Release to support Customer info feature.
• Bumped parent version 1.2.9
• Bumped Common version 1.3.3
• Bumped Clients version 1.3.2
• Bumped auth version 1.3.2
• Bumped jwkms version 1.3.2

Feature and fixes

• Feature: Customer Info
  • Update PSU creation scripts to create FRCustomerInfo in the datastore
  • Add new permission ReadCustomerInfoPSU
  • Add logic to handle new ReadCustomerPSU permissions
  • RCS needs to implement new CustomerInfo consent dialog

Transitive Feature and fixes

• N/A

Component releases table

Component	Current releases
Starter parent
Common
Clients
jwkms
auth

Release 1.6.0

Description

• Final Release to support VRP payments.
• Bumped parent version 1.2.8
• Bumped Common version 1.3.1
• Bumped Clients version 1.3.1
• Bumped auth version 1.3.1
• Bumped jwkms version 1.3.1

Feature and fixes

• Feature: VRP payments

Transitive Feature and fixes

• N/A

Component releases table

Component	Current releases
Starter parent
Common
Clients
jwkms
auth

Release 1.5.6

45: Use fixed uk-datamodel for 3.1.8

OBFundsConfirmationConsentResponse1Data uses OBExternalRequestStatus1Code rather than the StatusEnum
defined within the class.

Changes to converters to work with the newer OB Funds Conformation classes in the 3.1.8r5 swagger models.

Issue: OpenBankingToolkit/openbanking-toolkit#45

Release 1.5.5

Description

• UI redirection customer experience

Feature and fixes

• Feature 794

Transitive Feature and fixes

• N/A

Component releases table

Component	Current releases
Starter parent
Common
Clients
jwkms
auth

Release 1.5.4

Use latest parent and commons.

Release 1.5.3

797: Database upgrade does not save authorisationNumber

Issue: ForgeCloud/ob-deploy#797

Release 1.5.2

Adds database up grade steps to upgrade existing TPP records.
Introduces a test to ensure that MATLS transport cert and Software Statement belong to the same entity.

ForgeCloud/ob-deploy#796
ForgeCloud/ob-deploy#795

Done as part of the epic;
ForgeCloud/ob-deploy#775