Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...



Delegation info PIP
No delegationService ProviderEntitled PartyAuthorization Reg
Use case variation11a1b1c


Note that interaction sequences are not described in the table above. In derived use case 1c, two interaction sequences are possible depending on who requests delegation info from the PIP:

...

  1. The Machine Service Consumer requests a service from the Service Provider;
  2. The Service Provider authenticates the Machine Service Consumer and validates the iSHARE adherence of the Service Consumer;

  3. The Service Provider requests delegation evidence from the Authorization Registry;
  4. The Authorization Registry authenticates the Service Provider and validates its iSHARE adherence;
  5. The Authorization Registry authorizes authorises the Service Provider based on the scheme agreements for providing delegation information;
  6. The Authorization Registry provides the delegation evidence;
  7. The Service Provider validates the received delegation evidence through the following steps:
    1. The Service Provider authenticates the Authorization Registry and validates its iSHARE certification;
    2. The Service Provider authorizes authorises the Entitled Party based on the entitlement information registered with the Service Provider, and validates its iSHARE adherence.
  8. The Service Provider authorizes authorises the Machine Service Consumer of the Service Consumer based on the validity of the delegation evidence;
  9. The Service Provider executes the requested service;
  10. The Service Provider provides the service result to the Machine Service Consumer.

...