|
+2.5.2 Federated Digital Identity Model With General-Purpose IdP |
2.5.2 Federated Digital Identity Model With General-Purpose IdPFig. 4. Federated digital identity model example
Figure 4 shows an example of those same common interactions in a federated model. 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 in the identity service as a subscriber.
A subscriber account and corresponding authenticators are established between the CSP and the subscriber.
The IdP is provisioned either directly by the CSP or indirectly through access to attributes of the subscriber account. The CSP maintains the subscriber account, its status, and the enrollment data collected in accordance with the records retention and disposal requirements described in Sec. 3.1 of [SP800-63A]. The subscriber maintains their authenticators. The IdP maintains its view of the subscriber account, any federated identifiers assigned to the subscriber account, and any policies and decisions regarding the release of attributes and information to RPs.
The usual sequence of interactions involved in using one or more authenticators in the federated model to perform digital authentication is as follows: Step 3: The RP requests that the claimant authenticate and requests any attributes needed from the IdP to make access or authorization decisions. This triggers a request for federated authentication to the IdP.
Step 4: The claimant proves possession and control of the authenticators to the verifier function of the IdP through an authentication process.
The binding of the claimant’s authenticators are verified with those bound to the claimed subscriber account and optionally to obtain additional subscriber attributes.
Step 5: The RP and the IdP communicate through a federation protocol. The IdP provides an assertion and any necessary additional attributes to the RP through a federation protocol. The RP verifies the assertion to establish confidence in the identity and attributes of a subscriber for access to an online service at the RP. RPs use a subscriber’s federated identity (pseudonymous or non-pseudonymous), IAL, AAL, FAL, and other factors to make authorization decisions.
Step 6: An authenticated session is established between the subscriber and the RP.
1. Pregled
1.1 Reference1.2 Utvrđeni zahtjevi1.3 Povezani propisi2. Utvrđeni zahtjevi
3. Povezani propisi
|
