Skip to main content

INFOSEC-REVOCATION-VIA-ARRANGEMENT-REVOKE-ENDPOINT

NameVerify that on consent cancellation from the Holder Dashboard a Revocation request to the Data Recipient's Arrangement Revocation Endpoint
Category

INFOSEC

Execution Method

AUTOMATED (FAPI BIZA)

DescriptionVerify that on consent cancellation from the Holder Dashboard a Revocation request to the Data Recipient's Arrangement Revocation Endpoint
PreconditionsConsent must be established
Steps
  1. Establish a consent arrangement and verify its setup within the data recipient
  2. Retrieve the CDR Recipient base URI from the Register and construct the revocation URL as (RecipientBaseUri)/arrangements/revoke
  3. Disable the Recipient Base URI
  4. Initiate an arrangement cancellation from the Data Holder’s Dashboard
  5. Verify that the Holder has constructed and attempted to send a payload containing:
    • Uses the POST method for the request
    • cdr_arrangement_id parameter
    • Is sent using application/x-www-form-urlencoded with, optionally, a charset
    • Uses a signed JWT presented in the Bearer header for authentication
    • Contains the following claims within the JWT:
      • iss matching Data Holder Brand Identifier
      • sub containing the Data Holder Brand Identifier
      • aud containing the Data Recipient Client Identifier assigned by the Holder
      • exp an epoch timestamp that is a time in the future
      • jti an identifier for the JWT request
  6. Verify that the Holder failed to send the Revocation request due to Data Recipient being offline
  7. Bring the Recipient Base URI back online
  8. Verify a resend of (5) is received at the designated endpoint URL
Inputs
  • Dynamic Client Registration details
  • Recipient Holder details
  • Established Consent agreement
Expected Results
  • The Recipient accepts the request and processes it without an explicit error for the first round
  • The Holder submits the request to the correct endpoint location
  • The tokens issued to a recipient are revoked