Guide 3. Request participant evidence

In the DSGO, it is determined before a data transaction takes place whether all organisations involved in the data transaction are participants of the DSGO. If this is the case, both parties can rely on the DSGO legal framework for the data transactions. This page explains how a party can obtain participant evidence of another party at the Participant Registry.

---

Scenario

Organization A, in the role of Data service consumer, intends to use a data service offered by Organization B, in the role of Data service provider. Both parties can verify, prior to the data transaction, whether the other party is a participant of the DSGO. This verification ensures that the data transaction takes place under the legal contract both parties have signed with digiGO as governance body.

Sequence diagram

The diagram below outlines the steps for obtaining partyInfo object from the /parties endpoint of the Participant Registry. Organisation A first requests an access_token from the Participant Registry. Organisation A implemented a Client that can access a data service. The Participant registry handles the token request as a standard authentication flow.

Organisation A uses the access_token to request partyInfo of Organisation B from the Participant registry. Organisation A can verify if the partyInfo of Organisation B is valid. This validation can be used by Organisation A to request an access_token from Organisation B.

Organisation B can use the same flow to request party_info of Organisation A from the Participant Registry. This validation can be used by Organisation B to provide an access_token to Organisation A.

---

Sandbox environment: Test Participant Registry

digiGO offers the Participant registry in a test setting. This allows you to test your implementation of the above flow.

The Test Participant Registry can be used in a chain test where multiple organisations want to validate their implementations as data service consumers, data service providers, and authorization registries.

In order to use this Participant registry you can request an iSHARE test certificate , but a valid eIDAS certificate can also be used.

After successful registration you can use our Participant Registry API on our acceptance environment: https://api.acceptance.digigo.nu

When requesting an access token from the DSGO (test) participant registry, please use "aud":"did:ishare:EU.NL.NTRNL-63202158" in the payload of your client assertion JWT (the NTRNL of digiGO).

---

Further reading

Source	Description	Author	Language
/parties	DSGO specification of the /parties endpoint.	digiGO	English
partyInfo	Definition of the partyInfo object.	digiGO	English
DSGO Participant Test Registry	The DSGO Participant Test Registry for testing purposes	Centraal Register Techniek	English
iSHARE Code snippets	Github repository with code snippets for implementing iSHARE functionality.	iSHARE	English
iSHARE Test certificates	Tutorial how to request a Test certificate from iSHARE	iSHARE	English