Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space PDOIDC and version Moscow_OIDC
Error response
URLhttps://<xid-useradm-baseurl>/<pid>/consent
Request

DELETE with URL path parameter pid (same as bankid_altsub) for user in question

AuthenticationAccess Token as Bearer Token in Authorization Header
Success responseResponse
204No Content
Removal of consent was successful
403Forbidden
if the bearer
Bearer token is not accepted for any reason
400Bad
Request if
Request The pid is not an xID user or
if
resource access is insufficient (missing scope)

Error responses contains further information on the reason according to standard.

ExampleSee below

This method removes any consent registered on end user given by pid to use the xID service at the OIDC client identified by the azp in the Bearer Access Token. Hence, this method can only be use by an OIDC client to remove consents for its own xID-enabled service. There is no dialog shown to the end user.

...