Page Comparison

This part of the iSHARE Scheme Trust Framework is considered normative and is therefore compliant with RFC 2119.

One requirement to any legal entity fulfilling a role is that they MUST provide a unique identifier.

...

Please refer to the detailed Operation descriptions for what criteria need to be met to be admitted to the iSHARE network.

Anchor
Service Consumer Service Consumer

Service Consumer

The Service Consumer-role is fulfilled by a legal entity that consumes a service, such as data, as provided by a Service Provider. 

...

• iSHARE adherence is REQUIRED. 

Anchor
Service Provider Service Provider

Service Provider

The Service Provider-role is fulfilled by a legal entity that provides a service, such as data, for consumption by a Service Consumer.

...

• iSHARE adherence is REQUIRED;
• All user interfaces available in an iSHARE context MUST comply with the iSHARE's user interface requirements.

Anchor
Entitled Party Entitled Party

Entitled Party

The Entitled Party-role is fulfilled by a legal entity that has one or more rights to a service provided by a Service Provider, for example to data. These rights, or entitlements, are established in a legal relation between the Entitled Party and the Service Provider.

...

• iSHARE adherence is REQUIRED.

  Certified roles

  In line with guiding principle 3, iSHARE utilises the Afsprakenstelsel elektronische toegangsdiensten as a building block for certifying Identity Providers, Identity Brokers, and Authorization Registries. Therefore, to  become an iSHARE certified party, a legal entity MUST (first) be admitted to the Afsprakenstelsel elektronische toegangsdiensten (in the relevant role). The relevant roles include:

  • Authenticatiedienst and Middelenuitgever for potential Identity Providers;
  • Herkenningsmakelaar for potential Identity Brokers;
  • Machtigingenregister for potential Authorization Registries.
  • • Note: as it is the responsibility of the Service Provider to determine the Entitled Party, the Service Provider can choose to provide services where the Entitled Party is not admitted to iSHARE. In this event, the responsibilities of the Entitled Party are shifted to the Service Provider in question. This is particularly useful for Service Providers who have existing (smaller) customers, who do not have own systems, or are only an Entitled Party for services at a single Service Provider.

  
  

  ...

  Certified roles

  Please refer to the detailed Operation descriptions for what (other) criteria need to be met to be admitted to the iSHARE network.

  Anchor
  Identity Provider Identity Provider

  Identity Provider

  The Identity Provider-role is fulfilled by a legal entity whose tooling identifies and authenticates humans (and specifically, Human Service Consumers representing Service Consumers). An Identity Provider: 

  • Provides identifiers for humans;
  • Issues and manages credentials (i.e. a password or electronic keycard) to humans for humans;
  • Receive authentication requests from Service Providers;
  • Provides an online interface to authenticate humans based on their credentials;
  • Can hold information on authorisations of humans representing a Service Consumer;
    i.e. information indicating which humans are authorised to act on a Service Consumer's behalf.;
  • Can, after successful identification and authentication, on the basis of this information, identify and authenticate humans for Service Providers and determine whether the human representing a legal entity is authorised to take delivery of a service. ;
  • Can confirm whether this is the case the identity, authentication and authorisation information to the Service Provider. 

  ...

  The functional requirements applicable to Identity Providers are as follows:

  ...

  • The Identity Provider MUST have a clear agreement with the authorising entity concerning the process of allowing the registering, updating or removing of an authorisation;
  • The Identity Provider MUST prevent that a revoked authorisation is processed as a valid authorisation;
  • The Identity Provider MUST ensure that the identification and authentication process conforms to the Level of Assurance requested by the Service Provider;
  • The Identity Provider MUST conform to the service levels for Certified Parties as described here;
    
  • The Identity Provider MUST NOT claim accordance with a Level of Assurance for which it has not been certified by the Scheme Owner;
  • The processes of the Identity Provider MUST be in accordance with the Level of Assurance for which the Identity Provider has been certified;
  • iSHARE certification is REQUIRED;
  • All user interfaces available in an iSHARE context MUST comply with the iSHARE's user interface requirements.
    

  Anchor
  Identity Broker Identity Broker

  Identity Broker

  Different humans might hold identifiers at different Identity Providers. Also, Service Providers might need to connect to several Identity Providers. To make sure Service Providers do not need a relation with each Identity Provider individually, an Identity Broker is introduced. The Identity Broker-role is fulfilled by a legal entity that provides Service Providers access to different Identity Providers, and that offers humans the option to choose with which Identity Provider to identify and authenticate themselves throughout the iSHARE Scheme.

  ...

  The functional requirements applicable to Identity Brokers are as follows:

  • All responsibilities and functional requirements applicable to Afsprakenstelsel elektronische toegangsdiensten role Herkenningsmakelaar.The Identity Broker MUST provide users an interface to select their Identity Provider;
  • The Identity Broker MUST conform to the service levels for Certified Parties as described here;
  • The Identity Broker MUST NOT claim accordance with a Level of Assurance for which it has not been certified by the Scheme Owner;
  • The processes of the Identity Broker MUST be in accordance with the Level of Assurance for which the Identity Broker has been certified;
    
  • iSHARE certification is REQUIRED;
  • All user interfaces available in an iSHARE context MUST comply with the iSHARE's user interface requirements.

  Anchor
  Authorization Registry Authorization Registry

  Authorization Registry

  The Authorization Registry-role is fulfilled by a legal entity who provides solutions for adhering parties Adhering Parties for the storage of delegation - and authorisation information. An Authorization Registry: 

  • Can hold information on delegations to Service Consumers;
    i.e. information indicating what parts of the rights of an Entitled Party are delegated to a Service Consumer.;
  • Has a process in place allowing for the registration, update and revocation of delegations;
  • Can check, on the basis of this information, whether a machine representing a legal entity is authorised to take delivery of a service;
  • Can confirm whether this is the case to the Service Provider. 

  As a result, Adhering Parties can outsource tasks concerning the management of authorisation and delegation information to an Authorization Registry instead of implementing their own tooling.

  The functional requirements applicable to Authorization Registries are as follows:

  ...

  • The Authorization Registry MUST have a clear agreement with the delegating entity concerning the process of allowing the registering, updating or removing of a delegation;
  • The Authorization Registry MUST prevent that a revoked delegation is processed as a valid delegation;
  • The Authorization Registry MUST conform to the service levels for Certified Parties as described here;
  • The Authorization Registry MUST NOT claim accordance with a Level of Assurance for which it has not been certified by the Scheme Owner;
  • The processes of the Authorization Registry MUST be in accordance with the Level of Assurance for which the Authorization Registry has been certified;
  • iSHARE certification is REQUIRED.