| Name | Verify that Arrangements established as Once Off or already Expired cannot be extended |
|---|
| Category | INFOSEC |
|---|
| Execution Method | AUTOMATED (FAPI BASELINE) |
|---|
| Preconditions | |
|---|
| Description | In this particular test an arrangement is established first as a once off and then as a short lived duration. For each scenario an attempt to reuse the arrangement is attempted (using the cdr_arrangement_id claim) and should be rejected.
Refer to: Extending an arrangement when it is expired or revoked |
|---|
| Steps | - Establish a once off consent agreement by specifying a sharing_duration of 0
- On completion of the consent flow perform Token and Arrangement ID collection using a POST /token
- Initiate an authorisation request requesting a sharing duration of 100 and specifying the CDR Arrangement ID retrieved within (2)
- The request should trigger an OAuth2 server error
- Establish a consent agreement by specifying sharing_duration of 360
- On completion of the consent flow perform Token and Arrangement ID collection using a POST /token and verify a sharing_duration_expires_at of < 360 seconds
- Wait 10 minutes
- Initiate an authorisation request requesting a sharing duration of 100 and specifying the CDR Arrangement ID retrieved within (6)
- The request should trigger an OAuth2 server error
|
|---|
| Inputs | Established Dynamic Client Registration |
|---|
| Expected Results | - The Holder should reject reuse of arrangements which were established as once-offβs
- The Holder should reject use of arrangements which are already expired
|
|---|