Headers Configuration

4 Headers Configuration

There are three types of headers configuration available for Berlin Open Banking.

System Headers (i.e. Mandatory Headers and its respective value validation)
Configuration Headers (i.e. Mandatory Headers).
API Configuration Headers (i.e. Mandatory Headers of a specific API)

Below are the configuration steps and Out of the box header already configured in the system.

System Headers: Both Header name and Header value are validated for System Headers.

For configuring more system headers, below script is to be executed in the OBAPI Admin schema.

Insert into DIGX_FW_CONFIG_ALL_B (PROP_ID, CATEGORY_ID, PROP_VALUE,FACTORY_SHIPPED_FLAG, PROP_COMMENTS, SUMMARY_TEXT, CREATED_BY,CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATED_DATE,
        OBJECT_STATUS,OBJECT_VERSION_NUMBER) values ('berlin.%%HEADERNAME%%','OpenbankingSystemHeaders','%%HEADERVALUE%%','N',null,'Open
        Banking','ofssuser',sysdate,'ofssuser',sysdate,'Y',1);

Below Query is used to check the System Headers in the system

select * from digx_fw_config_all_b where category_id = 'OpenbankingSystemHeaders';

Configuration Headers: As of now in OOTB one header has been added as mandatory - “X-Request-ID”. This header is required to be sent by the TPP to the ASPSP mandatorily with any value.

Only header name is validated in case of Configuration Headers.

For configuring more config headers, below script is to be executed in the OBDX/OBAPI Admin schema.

Insert into DIGX_FW_CONFIG_ALL_B (PROP_ID, CATEGORY_ID, PROP_VALUE, FACTORY_SHIPPED_FLAG, PROP_COMMENTS, SUMMARY_TEXT, CREATED_BY,
        CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATED_DATE, OBJECT_STATUS, OBJECT_VERSION_NUMBER)values ('berlin.%%HEADER NAME%%','
        OpenbankingConfigHeaders',null,'N',null,'OpenBanking','ofssuser',sysdate,'ofssuser',sysdate,'Y',1);

Below Query is used to check the System Headers in the system

select * from digx_fw_config_all_b where category_id = 'OpenbankingConfigHeaders';

API Configuration Headers : As of now in OOTB multiple headers have been added as mandatory. This header is required to be sent by the TPP to the ASPSP mandatorily with a corresponding suitable value.

Header name is validated if the entry is made for requested API only in case of API Configuration Headers.

For configuring more api config headers, below script is to be executed in the OBDX/OBAPI Admin schema.

Insert into DIGX_FW_CONFIG_ALL_B (PROP_ID, CATEGORY_ID, PROP_VALUE, FACTORY_SHIPPED_FLAG,
          PROP_COMMENTS, SUMMARY_TEXT, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY,
          LAST_UPDATED_DATE, OBJECT_STATUS, OBJECT_VERSION_NUMBER) values ('%%API_PATH%%.%%HTTP_METHOD%%',' OpenbankingApiConfigHeaders',%%HEADER NAME%%,'N',null,'Open
          Banking','ofssuser',sysdate,'ofssuser',sysdate,'Y',1);

Example: Insert into DIGX_FW_CONFIG_ALL_B (PROP_ID, CATEGORY_ID, PROP_VALUE, FACTORY_SHIPPED_FLAG, PROP_COMMENTS,    
        SUMMARY_TEXT, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATED_DATE, OBJECT_STATUS, OBJECT_VERSION_NUMBER) values  
        ('accounts/{account-id}/balances.GET','OpenbankingApiConfigHeaders',’Consent-ID’,'N',null,'OpenBanking','ofssuser',sysdate,'ofssuser',sysdate,'Y',1);

Below Query is used to check the System Headers in the system

select * from digx_fw_config_all_b where category_id = 'OpenbankingApiConfigHeaders';