|
+5.2 Federation Transaction |
5.2 Federation TransactionA federation transaction with a subscriber-controlled wallet establishes the subscriber’s device as an IdP for the subscriber account and creates an authenticated session for the subscriber at the RP. The process is shown in Fig. 13. Fig. 13. Federation with a subscriber-controlled wallet
A federation transaction with a subscriber-controlled wallet takes place over several steps: The CSP identity-proofs the subscriber and creates a subscriber account.
The CSP issues attribute bundles from the subscriber account to the wallet in a process that includes the subscriber verifying an authenticator in their subscriber account or completing an abbreviated proofing process (e.g., using a biometric captured at proofing to verify identity).
The wallet receives a signed attribute bundle from the CSP that allows the wallet to act as an IdP.
The RP requests a federated authentication transaction from the wallet, usually through subscriber action.
The subscriber activates the wallet through an activation factor. In the case of a hosted wallet, this is an authentication to the wallet service.
The wallet creates an assertion based on the RP request, subscriber actions, and attribute bundles that are available to the wallet.
The wallet presents the assertion to the RP.
The RP validates the assertion and creates an authenticated session for the subscriber. This process includes validating the attribute bundle from the CSP.
1. Přehled
1.1 Odkazy1.2 Identifikované požadavky1.3 Související regulace2. Identifikované požadavky
3. Související regulace
|
