Skip to main content

INFOSEC-INTROSPECTION-HAPPY

NameVerify that the introspection endpoint is available, contains minimal attributes, that only Refresh Tokens can be introspected and that Access and ID Token introspection requests are rejected
Category

INFOSEC

Execution Method

AUTOMATED (FAPI BIZA)

Description

In this particular test a series of introspection requests are made to verify that the introspection endpoint only accepts refresh tokens and that the attribute exposed via this endpoint are restricted

Preconditions
Steps
  1. Establish a consent agreement using the authorisation flow and receive the redirect containing the code and id_token attributes
  2. Perform Token retrieval using a POST /token
  3. Retrieve the introspection_endpoint from the OIDC discovery document
  4. Using the access_token retrieved from (2) attempt an introspection request to the introspection_endpoint. The request should be rejected
  5. Using the id_token retrieved from (2) attempt an introspection request to the introspection_endpoint. The request should be rejected
  6. Using the refresh_token retrieved from (2) perform an introspection request to the introspection_endpoint. The request should respond with a JSON payload containing the following fields:
    • active with a value of true
    • exp with a number aligned with an epoch equivalent to the expiration date of the consent agreement
InputsEstablished Dynamic Client Registration
Expected Results
  • The Holder must not support introspection of Access Tokens
  • The Holder must not support introspection of ID Tokens
  • The Holder must support introspection of Refresh Tokens but the introspection response must be limited to active and exp fields