Architecture
Introduction
The solution kit is organised in folders, it has a root folder called "OpenBanking PSD2" and under which there are 5 folders:
0-Fragments
1-DMZ
2-Internal usage services
3-XS2A
4-Mock
On top of these there are a few dependencies to consider like jdbc connections, identity providers, and Cluster-wide properties (CWP) that help
0-Fragments
this folder contains all the required dependency codes for customising and optimising the solution.
1-DMZ
This folder contains the DMZ part of the solution, where needed
2-Internal usage services
These are services that can be used to interface the Bank's (ASPSP) internal services with the PSD2 solution kit, this can be useful for the redirect flow and the consent revocation page.
3-XS2A
This folder contains all the XS2A services that are required for PSD2 compliance
4-Mock
This folder contains services to mock both TPP interaction and bank interaction.
CWP and other dependencies
on top of the policies and services, the solution relies on environment properties as well as jdbc connections and certificates, here is the list:
CWP
PSD2.V2.Framework
This CWP contains all the information regarding what needs to be used and where, any information about what the environment needs to do in order to be compliant with the standards of the ASPSP. It is in JSON format and each entry for each environment describes that environment
V2.env
This is a variable that is in place to tell the framework what the right settings are.
IDP
Name | Function |
---|---|
PSD2_QWAK | FIPS for TPP Mutual Authentication |
PSD2_QSealC | FIPS for TPP digest check |
Bank User Provider | A PBIDP for the authentication of mock users |
JDBC
Name | Function |
---|---|
PSD2_EBARegistry | For the storage of QTSP certificates, authorities and TPP Authorisation levels |
PSD2_live | For the Live PSD2 Storage |
PSD2_mock | For the Mock PSD2 storage |
PSD2_mock_bank | For the Mock bank DB |
Related pages
apiida.com