|
+5.3.1 CSPs and RPs |
5.3.1 CSPs and RPsTrust between the CSP and RP in subscriber-controlled wallet scenarios will not typically be bidirectional. In the general case, the RP trusts the CSP as the source of attribute bundles that are presented by subscriber-controlled wallets during a federation transaction, while the CSP is not expected to have direct knowledge of the RP. This trust relationship between the RP and CSP MAY be facilitated by a federation authority (see Sec. 3.5.2) that defines overarching trust agreements between members of an ecosystem representing RPs, CSPs, and subscriber-controlled wallets. Such trust agreements SHALL contain: The set of subscriber attributes and derived attributes that the CSP makes available to wallets in attribute bundles
The set of subscriber attributes and derived attributes that the wallet can make available to the RP
The population of subscriber accounts that the CSP can represent
The IALs or issuance processes of subscriber accounts that are associated with the attribute bundles from the CSP
The issuance process related to CSP attribute bundles
The FALs supported by subscriber-controlled wallets
The allowable purposes for each attribute RPs may request
Expectations of RPs for the protection and management of subscriber data provided through attribute bundles
Trust MAY also be established unilaterally by RP evaluation of publicly available information about CSPs and their processes for issuing attribute bundles. To facilitate this, CSPs SHALL publish the following information to a trusted location for RPs to evaluate: The set of subscriber attributes and derived attributes that the CSP makes available to wallets in attribute bundles
The set of subscriber attributes and derived attributes that the wallet can make available to the RP
The population of subscriber accounts that the CSP can represent
The IALs or issuance processes of subscriber accounts associated with the attribute bundles from the CSP
This information MAY be made available by a trusted third party, such as a federation authority that assesses and evaluates CSP attribute bundle issuance and makes CSP features available through a discovery service. Trust between RPs and CSPs MAY be accomplished in either a pre-established (see Sec. 4.3.1) or subscriber-driven fashion (see Sec. 4.3.2). For example, an RP could be statically configured to accept attribute bundles from only a specific set of CSPs for its purposes, or the RP could alternatively accept attribute bundles from any CSP by prompting the subscriber for consent at runtime. This trust relationship could also be made more explicit by the RP being provided a means of verifying CSP-approved subscriber-controlled wallet identifiers beyond the verification of the attribute bundle, such as a discovery service provided through a federation authority. 1. Преглед
1.1 Препратки1.2 Идентифицирани изисквания1.3 Свързани регулации2. Идентифицирани изисквания
3. Свързани регулации
|