|
+2.5.1 Non-Federated Digital Identity Model |
2.5.1 Non-Federated Digital Identity ModelFig. 3. Non-federated digital identity model example
Figure 3 shows an example of a common sequence of interactions in the non-federated model. Other sequences could also achieve the same functional requirements. One common sequence of interactions for identity proofing and enrollment activities is represented as follows: Step 1: An applicant applies to a CSP through an identity proofing and enrollment process. The CSP identity-proofs that applicant.
Step 2: Upon successful identity proofing, the applicant is enrolled into the identity service as a subscriber.
A subscriber account and corresponding authenticators are established between the CSP and the subscriber. The CSP maintains the subscriber account, its status, and the enrollment data. The subscriber maintains their authenticators.
Steps 3 through 5 can immediately follow steps 1 and 2 or be done at a later time. The usual sequence of interactions involved in using one or more authenticators to perform digital authentication in the non-federated model is as follows: Step 3: The claimant initiates an online interaction with the RP and the RP requests that the claimant authenticate.
Step 4: The claimant proves possession and control of the authenticators to the verifier function through an authentication process:
The verifier interacts with the CSP to verify the binding of the claimant’s identity to their authenticators in the subscriber account and to optionally obtain additional subscriber attributes.
The CSP or verifier functions of the service provider give information about the subscriber. The RP requests the attributes that it requires from the CSP. The RP optionally uses this information to make authorization decisions.
Step 5: An authenticated session is established between the subscriber and the RP.
1. Pregled
1.1 Sklici1.2 Ugotovljene zahteve1.3 Povezani predpisi2. Ugotovljene zahteve
3. Povezani predpisi
|
