iSHARE Developer Portal
Other resources
Version 2.0.1
Version 2.0.1
  • Welcome to the iSHARE Developer Portal
  • Introduction
    • Getting started
      • Test certificates
      • Test participants
    • Release info
    • Help & support
    • UI Guidelines
    • Conformance test tool
  • Roles
  • iSHARE Satellite role
    • Getting started
    • Access token (M2M)
    • Parties
    • Parties (single party)
    • Trusted list
    • Versions
    • Capabilities
    • Dataspaces
    • Create entitled party
  • Authorisation Registry Role
    • Getting started
    • Access token (M2M)
    • Delegation
    • Capabilities
  • Service Provider Role
    • Getting started
    • Access token (M2M)
    • Return
    • Service
    • Capabilities
  • Service Consumer Role
    • Getting started
  • Identity Provider
    • Getting started
    • Authorize
    • Login
    • Access token
    • User info
    • Capabilities
  • Entitled Party
    • Getting started
  • All roles (common endpoints)
    • Access token (M2M)
    • Capabilities
  • Reference
    • iSHARE JWT
      • Client Assertion
    • Authentication
    • Authorization
    • Delegation mask
      • Policy sets
    • Delegation evidence
      • Policy sets
    • Postman collections
Powered by GitBook
LogoLogo

  • Cookie Policy

  • Privacy Policy

  • Imprint

  • Contact Us

Copyright © 2024 iSHARE Foundation

On this page

Roles

PreviousConformance test toolNextGetting started

Last updated 2 months ago

One of the iSHARE Trust Framework's core features is its description of functional roles. These roles represent the different ways organisations can interact with each other. To assure federation of all aspects, and no single points of ‘failure’ or ‘power’ in the structure, all roles are defined and can be executed by multiple parties.

Role Definition

The principle of a role is that its execution can be done by the same legal entity, but the interface specification assures that always level playing field / federation is possible. The Trust Framework introduces two core role types: "Adhering Parties" and "Certified Parties”

"Adhering parties" directly engage with data and include:

  • : Organisations with rights to access specific services or data.

  • Organisations offering services for consumption.

  • : Organisations using services provided by service providers.

"Certified Parties" are certified to facilitate trusted exchanges between Adhering Parties. They encompass these specific roles:

  • : Organisations responsible for onboarding and trust assurance.

  • : Organisations providing Authorisation registry services.

  • : Organisations offering identification services for humans.

  • Identity Broker: Organisations serving as intermediaries between Service Providers and Identity Providers.

Data Owner or Entitled party
Service or Data Provider:
Service or Data Consumer
Satellite or Data Space Governance Body
Authorisation Registry
Identity Provider