Creates and provides a new access token. This method results in an access token with which the requesting party can gain access to a service at the providing party. The format of an access token is not defined by this specification. They are left to the server and should be opaque to a requesting party.
...
In OAuth 2.0 clients are typically “pre-registered” by the server. In the DSGO this is not desirable as data can be shared with previously unknown clients. Therefore client identification and authentication is performed via a check by the DSGO Trust Framework Authority via the Trust Framework catalog. For more details see the Access Token flow.
...
For information about the parameters that are common to trust framework’s API’s see Generic API Requirements.
...
Parameters | Description | |
---|---|---|
| Required | as the OAuth 2.0 grant type. MUST be equal to |
| Required | as the OAuth 2.0 scope. MUST contain the value |
| Required | as the OAuth 2.0 JWT bearer profile, specified in RFC7523. MUST contain a valid Organisation ID of the data service consumer, containing an EORI or KvK number. Used in DSGO for client identification. |
| Required | as the OAuth 2.0 JWT bearer profile, specified in RFC7523. MUST be equal to |
| Required | as the OAuth 2.0 JWT bearer profile, specified in RFC7523. MUST contain a signed JWT (Authentication JWT or Onweergbaarheid JWT). Used in DSGO for authentication of the client. |
...
For information about the parameters that are common to trust framework’s API’s see Generic API Requirements.
...