iSHARE's three primary use cases are supported by seven secondary use cases. These include:
...
| Panel |
|---|
3a. Register delegation at Service Provider, Entitled Party, or Authorization Registry
later, an Entitled Party needs to be able to: 3b. Modify delegation at Service Provider, Entitled Party, or Authorization Registry |
When authorising authorizing something or -one, the Service Consumer needs to:
| Panel |
|---|
4a. Register authorisation authorization at Service Provider, Entitled Party, or Authorization Registry
later, a Service Consumer needs to be able to: 4b. Modify authorisation authorization at Service Provider, Entitled Party, or Authorization Registry |
Processes that recur in primary use cases
...
In any primary use case, the Service Provider also needs to:
| Panel |
|---|
6. Determine an authorisation authorization decision based on entitlement-, delegation-, and/or authorisation authorization info in its own contract administration and/or from external PIPs |
When delegation- or authorisation authorization info is requested by a Service Provider, an Authorization Registry or Entitled Party also needs to:
| Panel |
|---|
7. Determine authorisation authorization decision based on Service Consumer assertion included in Service Provider’s request |
...