Trust Framework Setup
...
Reference Data
Roles

Metadata

This section covers Metadata in Raidiam Connect. They are part the platform configuration available in Reference Data.

More information on Reference Data can be found here.

Authorisation Domain Roles Metadata

Purpose and Functionality

  • Ecosystem administrators have the ability to link specific Authorisation Domain Roles to technical authorisations within applications. This process involves associating these roles with technical OAuth scopes and grant types.
    • Each Authorisation Domain Role can be associated with specific OAuth metadata types, dictating the permissions and access levels within the role.

Example Application

  • For instance, in the 'Open Banking' Authorisation Domain, the 'PISP' (Payment Initiation Service Provider) role might be linked with OAuth scopes like 'openid' and 'payments', and an OAuth grant type of 'authorisation_code'. This linkage defines the technical permissions and capabilities associated with the role.

Here is a table detailing various examples of how Authorisation Domain Roles are linked with specific technical metadata:

Authorisation Domain

Authorisation Domain Role

Technical Metadata Type

Technical Metadata Value

PSD2

PISP

scope

openid payments

PSD2

PISP

grant_type

authorisation_code

Open Banking

DADOS

response_type

code id_token

Retail Banking

Data Provider

scope

make:payments

Commercial Banking

Data Receiver

grant_type

authorisation_code

  1. Scope (PSD2 - PISP)
    • The 'openid payments' scope allows the PISP role to access open banking identity and payment services within the PSD2 framework.
  2. Grant Type (PSD2 - PISP)
    • The 'authorisation_code' grant type is used for obtaining an authorization code as part of the authentication process.
  3. Response Type (Open Banking - DADOS)
    • The 'code id_token' response type specifies that the application will receive an authorization code and an ID token upon successful authentication.
  4. Scope (Retail Banking - Data Provider)
    • The 'make:payments' scope enables the Data Provider role in Retail Banking to initiate payment transactions.
  5. Grant Type (Commercial Banking - Data Receiver)
    • Similar to the PSD2 PISP role, the 'authorisation_code' grant type in Commercial Banking facilitates the authorization process for data receivers.