Skip to main content

INFOSEC-REVOCATION-ARRANGEMENT-ENDPOINT-EXISTS

NameVerify that the Holder is publishing a CDR Arrangement Revocation Endpoint
Category

INFOSEC

Execution Method

AUTOMATED (FAPI BIZA)

Description

In this particular test the user has an established sharing arrangement and chooses to cancel it from the Recipient. In this scenario, the Recipient submits a revocation request to the Holder’s CDR Arrangement Revocation endpoint specifying an arrangement identifier and secured using a private_key_jwt client assertion.

Preconditions

Consent must be established

Steps
  1. Verify that the cdr_arrangement_revocation_endpoint attribute exists and is usable from the OpenID Connect Discovery document
  2. Establish a consent arrangement and verify it’s setup within the data recipient
  3. Cancel the consent arrangement and verify that the revocation is processed with the following attributes:
    • Uses the POST method for the request
    • cdr_arrangement_id parameter
    • Is sent using application/x-www-form-urlencoded
    • Uses private_key_jwt for authentication
  4. 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
  5. Re-execute (3) a second time and verify it is now throwing an error code of 422 due to cdr_arrangement_id being reused
  6. Re-execute (2) and (3) using a duplicate jti and verify rejection
  7. Re-execute (3) using an exp value in the past
  8. Re-execute (3) omitting private_key_jwt authentication and verify rejection
  9. Re-execute (3) using the DELETE method within the request and verify it is rejected
  10. Re-execute (3) using a valid request content (verified in the first run of (3)) but with the character set set to UTF-8 and verify it succeeds
Inputs
  • Dynamic Client Registration details
  • Recipient Holder details
  • Established Consent agreement
Expected Results
  • The Holder accepts the request for valid revocations
  • The Holder rejects requests using duplicate jti
  • The Holder rejects requests using an expired JWT
  • The Holder rejects requests without private_key_jwt authentication
  • The Holder rejects requests using the DELETE method
  • The Holder accepts requests with or without a character set defined