Releases: OpenBankingToolkit/openbanking-auth
Release 1.3.0
Description
- Final release to support
VRP payment
APIs. - Development version updated to 1.3.x
- Bumped starter-parent version 1.2.7
- Bumped Common version 1.3.0
- Bumped Clients version 1.3.0
Feature and fixes
- N/A
Transitive Feature and fixes
Component releases table
Component | Current releases |
---|---|
Starter parent | |
Common | |
Clients |
Release 1.1.13
45: Use fixed uk-datamodel for 3.1.8
OBFundsConfirmationConsentResponse1Data uses OBExternalRequestStatus1Code rather than the StatusEnum
defined within the class.
Release 1.1.12
Includes latest 3.1.8r5 tag swagger generated models
Release 1.1.11
Use latest parent and commons;
Allow creation of OBRIRoles from PSD2Role
Also;
Pulls in 1.0.3 of spring-security-mult-auth that has improved logging
Release 1.1.10
Release 1.1.9
Contains #152
796: Add MATLS checks to DCR code
Common code needed to perform MATLS checks to ensure the MATLS transport
cert presented for registration and the software statement being used
for registration were issed to the same ApiClient (TPP)
Issue: ForgeCloud/ob-deploy#796
Release 1.1.8
Use latest commons with fix to ensure iss field is visible in DirectorySoftwareStatement serialisation.
Also includes fix to add iss field to SoftwareStatement issued by the Directory Server.
Includes #140
Release 1.1.7
793: Use latest master with fixed serialisation
Issue: ForgeCloud/ob-deploy#793
Release 1.1.6
Use v 1.2.7 of openbanking commons
https://github.com/OpenBankingToolkit/openbanking-common/releases/tag/1.2.7
Fixes;
Serialisation is based on the value of the iss
field of the software
statement, and the code expected OpenBanking iss to be "OpenBanking",
however in OB Directory Issued Software Statements the iss field is
actually "OpenBanking Ltd"
Issue: ForgeCloud/ob-deploy#793
Release 1.1.5
Use latest commons with serialisable DirectorySoftwareStatement #144