| Name | Verifies that a Holder synchronises ADR Software Product state changes from Register |
|---|
| Category | INFOSEC |
|---|
| Execution Method | AUTOMATED (FAPI BASELINE) |
|---|
| Preconditions | - A dynamic client registration has been completed
- 2 x Active Consent agreement with multiple accounts belonging to multiple product categories
- Data Recipient is set to Active in the register
- Associated Software Product is set to Active in the register
|
|---|
| Description | In this particular test a functional Data Recipientโs Software Product has its Status altered by the Register and the Holder is tested to ensure it alters behaviour of the Software Productโs assigned client identifier. |
|---|
| Steps | - Initiate GET /banking/accounts using the pre-established token related to the Arrangement A and specifying an x-fapi-interaction-id with x-v set to 1
- Initiate GET /banking/accounts using the pre-established token related to the Arrangement B and specifying an x-fapi-interaction-id with x-v set to 1
- The request should succeed.
- Update the Software Product within the Register to Inactive. Wait 10 minutes.
- Attempt (1) again, the request should be rejected.
- Attempt to initiate a new arrangement request, the request should be rejected.
- Attempt to perform a token refresh for Arrangement A, this may be rejected depending on Holder configuration.
- Issue a Revocation request for Arrangement Aโs token, this should succeed.
- Update the Software Product within the Register to Active. Wait 10 minutes.
- Attempt to perform a token refresh for Arrangement B
- Attempt (2) again, the request should succeed
- Update the Software Product within the Register to Removed. Wait 10 minutes.
- Attempt (2) again, the request should be rejected
- Attempt to initiate a new arrangement request, the request should be rejected.
- Attempt to perform a token refresh for Arrangement B, this should be rejected
- Verify that the Holder dashboard has revoked all consents for the Software Product
- Attempt to perform GET /register/{ClientId} to obtain Client Details for the Client Registration. This should fail with error 400.
|
|---|
| Inputs | - A client registration for the Software Product
- Two established arrangements
|
|---|
| Expected Results | - When a Software Product changes to Inactive, the Holder should suspend sharing but maintain revocation operations for Refresh Tokens
- When a Software Product recovers to Active, the Holder should resume sharing of normal operations
- When a Software Product changes to Removed the Holder should revoke all agreements and delete the Client Registration
|
|---|