Secondary use cases

iSHARE Trust Framework's three primary use cases are supported by seven secondary use cases. These include:

• Processes related to registration;

• Processes that recur in primary use cases.

Processes related to registration

These four secondary use cases need to be completed before any specific, primary use cases can be initiated.

Any party needs to:

1a. Register adherence/certification in the Participant Registry

And later needs to be able to:

1b. Modify adherence/certification in the Participant Registry

Before initiating Human to Machine use cases, the Service Consumer needs to:

2a. Create Service Consumer and/or Human Service Consumer identity at Identity Provider. Prerequisites:

• An agreement needs to be in place between the Service Consumer and the Identity Provider.

Later, a Service Consumer needs to be able to:

2b. Modify Service Consumer and/or Human Service Consumer identity at Identity Provider

When delegating rights, the Entitled Party needs to:

3a. Register delegation at Service Provider, Entitled Party, or Authorisation Registry. Prerequisite:

• For registration at the Service Provider or Authorisation Registry, an agreement needs to be in place between the Entitled Party and the Service Provider or Authorisation Registry.

Later, an Entitled Party needs to be able to:

3b. Modify delegation at Service Provider, Entitled Party, or Authorisation Registry

When authorising something or one, the Service Consumer needs to:

4a. Register authorisation at Service Provider, Entitled Party, or Authorisation Registry. Prerequisite:

• For registration at the Service Provider or Authorisation Registry, an agreement needs to be in place between the Service Consumer and the Service Provider or Authorisation Registry.

Later, a Service Consumer needs to be able to:

4b. Modify authorisation at Service Provider, Entitled Party, or Authorisation Registry

Processes that recur in primary use cases

These three secondary use cases form the wiring of all primary use cases. Without them, primary use cases cannot be completed successfully.

In any primary use case, any party needs to:

5a. Check whether its counterparty is iSHARE adherent/certified (with the Participant Registry)

5b. Check whether its counterparty’s certificate is valid

In any primary use case, the Service Provider also needs to:

6. Determine an authorisation decision based on entitlement-, delegation-, and/or authorisation info in its own contract administration and/or from external PIPs

When delegation- or authorisation info is requested by a Service Provider, an Authorisation Registry or Entitled Party also needs to:

7. Determine authorisation decision based on the Service Consumer assertion included in the Service Provider’s request

Please note that the secondary use cases will not be detailed further than the above. No depictions or sequence diagrams are to be developed (contrary to those for the primary use cases). This (deliberately) leaves freedom in implementation. This specifically accounts for the registration of delegations: the way in which delegations are registered (as policies, business rules, in a separate register, or on top of existing applications) is not defined.