The improvements (e.g.,bug fixes, security fixes) for the lately released WSO2 Open Banking v1.3.0 are documented here. You can download WSO2 Update Manager (WUM) and update the existing product. WUM is a command-line utility that is used to distribute improvements that are released by WSO2 Open Banking on top of a released version. With WUM updates, you can get the fixes you want without waiting for the next release of the product. WUM is accessible via a subscription, but you can try the 15-day trial here.
In order to download the latest version of WSO2 Open Banking, you need to use WUM. Following are the instructions on how to use WUM for downloading the product and its updates.
Set up the WSO2 Update Manager (WUM).
WUM is a simple command-line tool that connects to the WSO2 update service, determines which updates are new and relevant, and downloads them. You can get the latest version of the WSO2 Open Banking product packs through WUM.
You need a WSO2 subscription to start using the WSO2 Update Manager.
Add the necessary product packs using the commands given below:
Update the product packs using the commands given below:
Additionally, download and update the other instances of WSO2 Open Banking product.
The product packs reside in the
<Product_name-<version>+<timestamp>.full.zip. Copy the product packs to a preferred location in each node, and extract them.
This document refers to the file paths of the product packs for the Key Manager, API Manager, API Manager Analytics, and Enterprise Integrator as
Following are the updates for WSO2 Open Banking 1.3.0 version.
|Released Date||Update Description|
|According to the OBIE the Account Servicing Payment Service Providers (ASPSPs) need to make sure that the TPPs can be registered in a seamless, ideally a fully automated process. The Dynamic Client Registration(DCR) endpoint is capable of dynamically registering the clients with the ASPSP when the client sends a registration request with its metadata. Click here to see how to deploy DCR v3.2 API.|
|An improvement for Berlin specification compliant solution in WSO2 Open Banking. Verifies if an account-id sent within the account-consents resource that is sent by TPP, is valid from the bank back-end. For the required configurations, see here.|
Allows users to validate the incoming request to APIs, based on any customizations done to a swagger definition. Follow the instructions given below to apply the update:
Click here to see the steps...
Click here to see the steps...
You need to re-publish the API to apply the swagger based validations. Therefore, Sign in to the API Publisher at https://<WSO2_OB_API-M_HOST>/9443/publisher using the credentials of a user, whose role is an API Publisher. For more information on users and roles, see here.
WSO2 Open Banking improved UK specific payment swagger files of version-3 APIs as its existing data definitions do not allow swagger-based validations. Following are the improved swagger files:
Make sure you add required customizations to the swagger file and upload the updated swagger file before re-publishing the API.
Validates PSD2 roles in the eiDAS QWAC (Transport Layer Certificate) during Berlin API Calls and restrict TPP accessing APIs if the required roles are not available in the certificate.
Allows the use of the DCR
|Improved the solution by validating the TPP when retrieving a payment submission. This validation confirms whether it is the same TPP that submitted the consent, is viewing the payment submission.|
Separates the redirect URI validation and the hostname validation for all the URIs in the request and changes the
Restricts RS256 signed messages from TPP. OBIE (Open Banking Implementation Entity) allowed both RS256 in addition to PS256 as the signature for signing JSON Web Signature (JWS). When market adopts RS256 sufficiently, RS256 has to be deprecated from signing JWS. As WSO2 Open Banking is an OBIE compliant solutions, this WUM update was released to deprecate the use of RS256. It includes the following changes: