This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.
Configuring the Open-Banking.xml File for AU
- Former user (Deleted)
- Former user (Deleted)
Configure open-banking.xml files in both WSO2 Open Banking Key Manager (WSO2 OB KM) and WSO2 Open Banking API Manager (WSO2 OB APIM) components based on the configurations listed below.
The open-banking.xml files are in below locations:
<WSO2_OB_KM_HOME>/repository/conf/finance/open-banking.xml<WSO2_OB_APIM_HOME>/repository/conf/finance/open-banking.xml
Do the following configurations in both the Key Manager and API Manager components and restart the servers.
| Configuration | |
|---|---|
| 1 | Define the specification that you plan to deploy. Possible values: <DeployedSpecification>AU</DeployedSpecification> |
| 2 |
<SharableAccountsRetrieveEndpoint>http://<WSO2_OB_APIM_HOST>:9763/open-banking/services/bankaccounts/bankaccountservice/sharable-accounts</SharableAccountsRetreiveEndpoint>
In the default WSO2 Open Banking solution, an API is exposed to return shareable accounts when the user_id is passed. The given JSON response must be returned and then it automatically loads the accounts list in the consent page. {
"data": [
{
"account_id": "1234-2345-3456-4567",
"display_name": "1234-2345-3456-4567"
},
{
"account_id": "9999-4345-8456-4567",
"display_name": "9999-4345-8456-4567"
}
]
}
By default, mock back end deployed in http://<WSO2_OB_APIM_HOST>:9443/as400/sharable-accounts/{userId}
|
| 3 | Metadata management: ACCC does not support this feature yet. To try out the feature before the ACCC endpoints are available, create a mock back end and invoke the hosted services. Once ACCC creates its status discovery endpoints, the Data Holder should configure the following properties under |
| 4 | Support for extended endpoints and holder specific version handling: By default, the following resources are configured in the solution. To add additional resources to the Consumer Data Standards API, add an entry under To define a Data Holder specific identifier for extended API endpoints, configure the following in WSO2 Open Banking API Manager. For example, if the Data Holder is ABC-Bank. |
| 5 | To cache the responses received for the CDS API requests, update the following configurations in WSO2 Open Banking API Manager: <Enforcement> <Cache> <CacheEnabled>true</CacheEnabled> <ModifiedExpiryMinutes>15</ModifiedExpiryMinutes> <AccessedExpiryMinutes>15</AccessedExpiryMinutes> </Cache> </Enforcement> |
| 6 | To configure Mutual Transport Later Security (MTLS) certificate bound access token, update the
See MTLS certificate bound access token, for more information. |
| 7 | If MTLS is terminated before the request reaches the Gateway, retrieve the Data Recipient's certificate from the MTLS session and include as a transport certificate header. By default, the gateway expects <CertificateManagement>
<!-- In order to enable the client certificate validation feature (Certificate Expiry, Signature and
Revocation validation during MTLS), the following module needs to be engaged under the "Global Engaged
Modules" section in the axis2.xml file.
<module ref="mtlscertvalidator"/>
-->
<!--Set the value of the transport certificate header sent in the request if MTLS is terminated before the
gateway default value is ssl.client.auth.cert.X509-->
<TransportCertificateHeader>ssl.client.auth.cert.X509</TransportCertificateHeader>
</CertificateManagement>
The load balancer should not allow the Data Recipient to send its certificate as a transport certificate header that is configured in the If such header was found in the Data Recipient's request, it is mandatory to remove that header from the Data Recipient's request. This is applicable even when the MTLS session is not terminated at the load balancer. When TLS is terminated before reaching the Gateway, to send the client certificate as a transport header, use the following configuration, which is placed just above the <ClientTransportCertAsHeaderEnabled>true</ClientTransportCertAsHeaderEnabled> <CertificateManagement> <!-- Expiry time for the cache (in seconds) for storing the validation result of the certificates--> <ClientCertificateCacheExpiry>3600</ClientCertificateCacheExpiry> <!-- Enable/Disable certificate OCSP and CRL validation. Default value has been set to true --> <CertificateRevocationValidationEnabled>true</CertificateRevocationValidationEnabled> </CertificateManagement> |
| 8 | This is for the Data Reporting feature, to enable data publishing set the <DataPublishing>
<!-- Include all configurations related to Data publishing -->
<!-- Enable data publishing in WSO2 Open Banking-->
<Enabled>true</Enabled>
<!-- Server URL of the remote BI server used to collect statistics. Must
be specified in protocol://hostname:port/ format. -->
<ServerURL>{tcp://<WSO2_OB_BI_HOST>:7612}</ServerURL>
<!-- Administrator username to login to the BI server for data publishing. -->
<Username>admin@wso2.com@carbon.super</Username>
<!-- Administrator password to login to the BI server for data publishing. -->
<Password>wso2123</Password>
</DataPublishing>
|
| 9 | By default, the Consent Management APIs are secured with basic authentication. To access the Consent Management APIs, use the default user or create a new user using the Key Manager Management Console.
For more information, see configuring basic authentication for Consent Management APIs. |
| 10 | Dynamic Client Registration configurations under
|