| Name | Verify that Arrangement Identifiers do not change if provided by Recipient |
|---|
| Category | INFOSEC |
|---|
| Execution Method | AUTOMATED (FAPI BASELINE) |
|---|
| Preconditions | |
|---|
| Description | In this particular test the recipient initiates a consent then attempts to update the consent using an existing arrangement id. |
|---|
| Steps | - Establish a consent agreement using the authorisation flow
- On completion of the consent flow perform Token and Arrangement ID collection using a POST /token
- Initiate an authorisation request via Request Object requesting a sharing duration double that requested in (1) as well as an additional scope (transaction detail) while specifying the CDR Arrangement ID retrieved within (2) as the cdr_arrangement_id. The request should fail.
- Initiate an authorisation request via Pushed Authorisation Request requesting a sharing duration double that requested in (1) as well as an additional scope (transaction detail) while specifying the CDR Arrangement ID retrieved within (2) as the cdr_arrangement_id. The request should succeed.
- Complete the consent flow with the consumer adding an additional account to the sharing arrangement
- On completion of the consent flow perform Token and Arrangement ID collection using a POST /token
- Verify that the arrangement identifier retrieved in (2) and reused in (3) remains the same in (4), that the sharing duration length has been extended and the available accounts has increased by one.
|
|---|
| Inputs | Established Dynamic Client Registration |
|---|
| Expected Results | - The Holder should not alter existing arrangement identifiers
- The sharing duration should be able to be extended
- Additional scopes should be able to be added
- Additional accounts should be able to be added
|
|---|