Without Identity Broker
This use case would look as follows without an Identity Broker:
Last updated
Version 2.1 (current version)
This use case would look as follows without an Identity Broker:
Last updated
It is prerequisite of this use case that:
The Service Provider has and manages its own authorization information indicating what Entitled Parties are entitled to what (parts of) services*;
The Service Consumer has and manages its own authorization information indicating which Human Service Consumers are authorized to act on its behalf**;
The delegation/authorization responsible at the Service Consumer registers the authorization information at the Authorization Registry;
The Service Provider is able to authenticate the Human Service Consumer;
The Identity Provider is able to authenticate the Service Provider;
The Service Provider is able to authenticate the Identity Provider;
The Human Service Consumer has been issued identity credentials by the Identity Provider.
In this use case, the Entitled Party is also the Service Consumer.
*The Service Provider can outsource this function to a third party
**The Service Consumer can outsource this function to a third party
The use case consists of the following steps:
(Numbers are intended to explain the use case flow, it might vary from the diagram due to multiple authorization methods)
The Human Service Consumer requests a service from the Service Provider.
The Service Provider asks the Human Service Consumer for their Identity Provider information.
The Human Service Consumer provides Identity Provider information to the Service Provider.
The Service Provider requests a login from the Identity Provider.
The Identity Provider requests credentials from the Human Service Consumer.
The Human Service Consumer provides credentials to the Identity Provider.
The Identity Provider authenticates the Human Service Consumer.
The Identity Provider provides an identity token to the Service Provider.
The Service Provider validates the Identity Provider’s iSHARE certification and the identity token of the Human Service Consumer.
The Service Provider validates the Human Service Consumer based on the authorization token (Refer to methods of authorization on how an authorization token is obtained)
The Service Provider validates authorization and iSHARE adherence of the Service Consumer.
The Service Provider executes the requested service and provides the service result to the Human Service Consumer.
Diagram 1: Authorization via Identity Provider Checking Authorization Registry (AR)
Diagram 2: Authorization via Participant Registry Verifying Service Consumer Before Authorization Check
Diagram 3: Authorization via Identity Provider Providing an Authorization Link to the Service Provider
