CIBA Consent Updater
When a user approves/rejects the consent via the mobile device, the response is sent to the Identity server from the mobile. Before the response data is persisted, it is possible to change the payload data.
You can use the CIBA Authentication Endpoint Consent Updater to change consent data that is sent from the CIBA mobile app before persisting them in the database. Extending the following class:
Given below is a brief explanation of the methods you need to implement.
This method lets you update the consent data that is sent from the mobile as a response.
public JSONObject updateConsentData(JSONObject consentData)
JSONObject consentData: consent data sent from the mobile app
updateConsentData: updated consent data
Configuring a custom CIBA Authentication Endpoint Consent Updater¶
- Once implemented, build a JAR file for your project.
- Place the above-created JAR file in the
- Open the
open_banking.identity.ciba_webapptag and configure your customization using the Fully Qualified Name (FQN). For example,
[open_banking.identity.ciba_webapp] Servlet_extension = com.wso2.openbanking.accelerator.consent.extensions.ciba.model.CIBAAuthenticationEndpointInterface
Save the configurations and restart the Identity Server.