Skip to main content

INFOSEC-REVOCATION-AT-RT-SUPPORT

NameVerify that the Holder supports both Access and Refresh Token revocation
Category

INFOSEC

Execution Method

AUTOMATED (FAPI BIZA)

DescriptionIn this particular test case the Holder must support both access and refresh token revocation such that a Data Recipient who chooses to notify the revocation endpoint with either type of token loses access to the Holder with that token.
Preconditions
Steps
  1. Establish an ongoing consent arrangement and verify its setup within the data recipient
  2. Utilise access_token to make request to the /banking/accounts endpoint containing:
    • x-fapi-customer-ip-address
    • x-fapi-interaction-id
  3. Issue a revocation request for the access_token to the Holder revocation endpoint
  4. Utilise access_token to make request to the /banking/accounts endpoint. If it succeeds mark this test as failed.
  5. Issue a revocation request for the refresh_token to the Holder revocation endpoint
  6. Attempt to perform a token refresh using POST /token and the previous refresh_token. If it succeeds mark this test as failed.
InputsEstablished Consent agreement
Expected Results
  • The Holder revokes the supplied AT when it is specified
  • The Holder revokes the supplied RT when it is specified