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
  1. Authorisation Registry Role

Getting started

PreviousCreate entitled partyNextAccess token (M2M)

Last updated 2 months ago

The Authorisation Registry role is fulfilled by a legal entity that provides solutions for Adhering Parties for the storage of delegation- and authorisation information. An Authorisation 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.

  • 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 for the Service Provider.

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

In order to double check if required endpoints are implemented, please use the following list as a cheat sheet:

Authorisation Registry

Access Token
Capabilities
Delegation