Skip to main content

INFOSEC-ADR-STATUS-CHANGES

NameVerifies that a Holder synchronises ADR Software Product state changes from Register
CategoryINFOSEC
Execution MethodAUTOMATED (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
DescriptionIn 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
  1. 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
  2. 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
  3. The request should succeed.
  4. Update the Software Product within the Register to Inactive. Wait 10 minutes.
  5. Attempt (1) again, the request should be rejected.
  6. Attempt to initiate a new arrangement request, the request should be rejected.
  7. Attempt to perform a token refresh for Arrangement A, this may be rejected depending on Holder configuration.
  8. Issue a Revocation request for Arrangement Aโ€™s token, this should succeed.
  9. Update the Software Product within the Register to Active. Wait 10 minutes.
  10. Attempt to perform a token refresh for Arrangement B
  11. Attempt (2) again, the request should succeed
  12. Update the Software Product within the Register to Removed. Wait 10 minutes.
  13. Attempt (2) again, the request should be rejected
  14. Attempt to initiate a new arrangement request, the request should be rejected.
  15. Attempt to perform a token refresh for Arrangement B, this should be rejected
  16. Verify that the Holder dashboard has revoked all consents for the Software Product
  17. 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