| Name | Verify 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) |
| Description | Verify that on consent cancellation from the Holder Dashboard a Revocation request to the Data Recipient's Arrangement Revocation Endpoint |
| Preconditions | Consent must be established |
| Steps | - Establish a consent arrangement and verify its setup within the data recipient
- Retrieve the CDR Recipient base URI from the Register and construct the revocation URL as (RecipientBaseUri)/arrangements/revoke
- Disable the Recipient Base URI
- Initiate an arrangement cancellation from the Data Holderβs Dashboard
- 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
- Verify that the Holder failed to send the Revocation request due to Data Recipient being offline
- Bring the Recipient Base URI back online
- 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
|