...
Excerpt |
---|
|
Panel |
---|
panelIconId | 2705 |
---|
panelIcon | :white_check_mark: |
---|
panelIconText | ✅ |
---|
bgColor | #FFF0B3 |
---|
| DSGO.Basis : Parties MUST support a POST call to a /token/revoke endpoint to revoke an access token
|
|
...
Excerpt |
---|
|
Panel |
---|
panelIconId | 2705 |
---|
panelIcon | :white_check_mark: |
---|
panelIconText | ✅ |
---|
bgColor | #FFF0B3 |
---|
| DSGO.Basis : Parties MUST validate that a POST request to a /token/revoke endpoint contains the HTTP headers as described in the table below
|
|
...
For information about the parameters that are common to trust framework’s API’s see Generic API Requirements.
Excerpt |
---|
|
Panel |
---|
panelIconId | 2705 |
---|
panelIcon | :white_check_mark: |
---|
panelIconText | ✅ |
---|
bgColor | #FFF0B3 |
---|
| DSGO.Basis : Parties MUST validate that a POST request to a /token/revoke endpoint contains the parameters as described in the table below
|
Panel |
---|
panelIconId | 2705 |
---|
panelIcon | :white_check_mark: |
---|
panelIconText | ✅ |
---|
bgColor | #FFF0B3 |
---|
| DSGO.Basis : Parties MUST validate the client credentials in the client_assertion received in a POST to a /token/revoke endpoint
|
|
Parameters | Description |
---|
grant_type
| Required | as the OAuth 2.0 grant type. MUST be equal to client_credentials . |
client_id
| 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. |
client_assertion_type
| Required | as the OAuth 2.0 JWT bearer profile, specified in RFC7523. MUST be equal to urn:ietf:params:oauth:client-assertion-type:jwt-bearer . |
client_assertion
| Required | as the OAuth 2.0 JWT bearer profile, specified in RFC7523. MUST contain a signed DSGO Authentication JWT. Used in DSGO for authentication of the client identification. |
token
| Required | as the OAuth 2.0 access token. MUST be equal to access token that the client wants revoked as specified in RFC7009 |
...
For information about the parameters that are common to trust framework’s API’s see Generic API Requirements.
200 OK
When the access token is successfully revoked, or an invalid token is submitted, the data service provider should send an OK result.
Excerpt |
---|
|
Panel |
---|
panelIconId | 2705 |
---|
panelIcon | :white_check_mark: |
---|
panelIconText | ✅ |
---|
bgColor | #FFF0B3 |
---|
| DSGO.Basis : Parties MUST respond with a 200 OK to a successful POST call to a /token/revoke endpoint
|
Panel |
---|
panelIconId | 2705 |
---|
panelIcon | :white_check_mark: |
---|
panelIconText | ✅ |
---|
bgColor | #FFF0B3 |
---|
| DSGO.Basis : Parties MUST respond with a 200 OK to a POST call to a /token/revoke endpoint containing an invalid access token
|
Panel |
---|
panelIconId | 2705 |
---|
panelIcon | :white_check_mark: |
---|
panelIconText | ✅ |
---|
bgColor | #FFF0B3 |
---|
| DSGO.Basis : Parties MUST no longer accept the revoked the access token after a 200 OK response is responded
|
|
...
Excerpt |
---|
|
Panel |
---|
panelIconId | 2705 |
---|
panelIcon | :white_check_mark: |
---|
panelIconText | ✅ |
---|
bgColor | #FFF0B3 |
---|
| DSGO.Basis : Parties MUST include the parameters as described in the table below in the HTTP payload in a response to a failed POST request to a /token/revoke endpoint
|
|
...
Excerpt |
---|
|
Panel |
---|
panelIconId | 2705 |
---|
panelIcon | :white_check_mark: |
---|
panelIconText | ✅ |
---|
bgColor | #FFF0B3 |
---|
| DSGO.Basis : Parties MAY include a Retry-After header in the 503 response to a /token/revoke endpoint to indicate the expected unavailability of the service
|
|