Consent Management APIs for UK

Consent Management APIs provide the capability to manage consents in a web application, on behalf of an end-user. A banking service consumer/ Account Servicing Payment Service Provider (ASPSP) may need to develop their own web application or use their own mechanism to deploy the consent management capabilities. At this point, a service provider needs a way to directly present consent resources to the end-user. In order to cater to this requirement, those consent capabilities (for example, consent creation/consent deletion) are presented as API resources in the Consent Management APIs.

You can log the Consent Management API calls in JSON format to a separate file. A sample log file is available here.

Add the following configurations to <WSO2_OB_KM_HOME>/repository/conf/finance/open-banking.xml.
```
<LogConsentInformation>true</LogConsentInformation>
```

Add the following properties to the <WSO2_OB_KM_HOME>/repository/conf/log4j.properties file. 
This is to save the log entries in the <WSO2_OB_KM_HOME>/repository/logs/transaction.log file in JSON format.

log4j.logger.TRANSACTION_LOGGER=INFO, TRANSACTION_LOGGER
log4j.appender.TRANSACTION_LOGGER=org.apache.log4j.FileAppender
log4j.appender.TRANSACTION_LOGGER.File=${carbon.home}/repository/logs/transaction.log
log4j.appender.TRANSACTION_LOGGER.Append=true
log4j.appender.TRANSACTION_LOGGER.layout=org.apache.log4j.PatternLayout
log4j.appender.TRANSACTION_LOGGER.layout.ConversionPattern=[%d] - %m %n
log4j.appender.TRANSACTION_LOGGER.threshold=INFO
log4j.additivity.TRANSACTION_LOGGER=false