Page Comparison

This is available only as a WUM update effective from January 03, 2021 (01-03-2021). For more information on updating WSO2 Open Banking, see Updating WSO2 Products.

1. Add the QSealC keypair corresponding to QWAC or OBSealC keypair corresponding to OBWAC  into a new JKS. For example, wso2carbon-signing.jks. 
2. Place the JKS file in the <WSO2_OB_APIM_HOME>/repository/resources/security directory.

3. Open the <WSO2_OB_APIM_HOME>/repository/conf/finance/open-banking.xml file:

   1. Add the following configs under the <CertificateManagement> section:

      • The SoftwareStatementId value needs to be configured according to the OBWAC/QWAC that has been configured in the <WSO2_OB_APIM_HOME>/repository/resources/security/wso2carbon.jks.

      • The OBIE service-related endpoints are for the OBIE sandbox environment.

        xml

   2. Configure the <SigningKeystore> tag with the file path of the JKS file that contains the OBSealC.

   3. Configure the <SigningCertificateAlias> and the <SigningCertificateKid> tags with the alias and KID value of the signing certificate (OBSealC):

      xml
4. Open the <WSO2_OB_APIM_HOME>/repository/resources/api_templates/velocity_template.xml file:

   1. Add the following handler as the first handler:

      xml

   2. Add the TPP validation handler after the #if($apiObj.additionalProperties.get("ob-spec") == "berlin") configuration as follows:

      xml
5. Republish your Accounts, Payments, and CoF APIs with the ob-spec, ob-api-version, and ob-api-type properties. For more information, see Deploying APIs for Berlin.
6. Open each API xml file(Accounts, Payments, and CoF APIs) in <WSO2_OB_APIM_HOME>/repository/deployment/server/synapse-configs/default/api and make sure that both APIPropertiesHandler and TPPValidationHandler are available.

Integrating a Custom Certificate Validation Service

If you want to integrate a custom validation service rather than OBIE, you can configure as follows:

1. Implement the following interface for the required certificate validation service.

   java
2. Once implemented, build a JAR file for your custom certificate validation service.
3. Place the above-created JAR file in the <WSO2_OB_APIM_HOME>/repository/components/dropins directory.
4. Open the <WSO2_OB_APIM_HOME>/repository/conf/deployment.toml file and find the [open_banking.cert_mgt.tpp_validation_service] tag.

5. Configure your TPP validation service using its Fully Qualified Name (FQN) as follows:

   xml

6. Add the following tags below the [open_banking.cert_mgt.tpp_validation_service] configurations:

   xml

7. Make sure you have the following handler as the first handler under the <Handlers> section in the <WSO2_OB_APIM_HOME>/repository/resources/api_templates/velocity_template.xml file. Otherwise add the handler.

   xml

8. Add the TPPValidationHandler handler right after the #if($apiObj.additionalProperties.get("ob-spec") == "berlin") configuration in the <WSO2_OB_APIM_HOME>/repository/resources/api_templates/velocity_template.xml file.

   xml
9. Republish your Accounts, Payments, and CoF APIs using publisher. Make sure that you have added the ob-spec, ob-api-version and ob-api-type properties before republishing the APIs.
10. Open each API xml file (Accounts, Payments, and CoF APIs) in <WSO2_OB_APIM_HOME>/repository/deployment/server/synapse-configs/default/api directory and make sure that both APIPropertiesHandler and TPPValidationHandler are added under the <handlers> section.