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 reference data docid 1va0dd53w2xgc28o4nxts 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 scope (psd2 pisp) the 'openid payments' scope allows the pisp role to access open banking identity and payment services within the psd2 framework grant type (psd2 pisp) the 'authorisation code' grant type is used for obtaining an authorization code as part of the authentication process 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 scope (retail banking data provider) the 'make\ payments' scope enables the data provider role in retail banking to initiate payment transactions 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