Consent Authorize
WSO2 Open Banking Accelerator consists of endpoints to manage consents. You can customize relevant functionalities of these consent endpoints according to your specification requirements using the OpenAPI based extension points available. This section explains the Consent Authorize component and how to customize its functionalities.
Note
Make sure to refer Developer guide for OpenAPI based extensions from documentation
The Consent Authorize extension point relates to the loading of the consent approval page and eventually persisting the consent provided by the users. This consists of 2 endpoints.
Populate Consent Authorization Screen¶
Note
This information that is sent and displayed on the consent page depends on the specification that you adhere to. The default consent page in WSO2 Open Banking
accelerator do support showing consent data and accounts data binding to the permissions.
OpenAPI Extensions¶
OpenAPI Extension | Description | OpenAPI Definition |
---|---|---|
populate-consent-authorize-screen | handle specification speicifc custom validations and set consent data and consumer data which need to show in consent grant UI | populate-consent-authorize-screen/post |
Configuration¶
To enable, follow the steps below:
-
Open the
<IS_HOME>/repository/conf/deployment.toml
file. -
Locate the following tag and enabke it as below and make sure allowed_extensions contains above table mentioned OpenAPI extensions.
[financial_services.extensions.endpoint]
enabled = true
base_url = "<BASE_URL_OF THE EXTENSION>"
allowed_extensions = [ "populate-consent-authorize-screen" ]
[financial_services.extensions.endpoint.security]
# supported types : Basic-Auth or OAuth2
type = "Basic-Auth"
username = ""
password = ""
Persist¶
The second extension point of the Consent Authorize component is the Persist Flow. The Persistent functionality is engaged once the
user approves/denies the consent via an API invocation made from the consent page. When the /persist
endpoint is
invoked, the OpenAPI extension implementation to persist are also invoked and the data required for persistence will be provided from the extension point.
OpenAPI Extensions¶
OpenAPI Extension | Description | OpenAPI Definition |
---|---|---|
persist-authorized-consent | handle user granted consent data storing | persist-authorized-consent/post |
Configuration¶
To enable, follow the steps below:
-
Open the
<IS_HOME>/repository/conf/deployment.toml
file. -
Locate the following tag and enabke it as below and make sure allowed_extensions contains above table mentioned OpenAPI extension.
[financial_services.extensions.endpoint]
enabled = true
base_url = "<BASE_URL_OF THE EXTENSION>"
allowed_extensions = ["persist_authorized_consent"]
[financial_services.extensions.endpoint.security]
# supported types : Basic-Auth or OAuth2
type = "Basic-Auth"
username = ""
password = ""
Top