| Name | Verify 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 | - Establish a consent agreement using the authorisation flow and receive the redirect containing the code and id_token attributes
- Perform Token retrieval using a POST /token
- Retrieve the introspection_endpoint from the OIDC discovery document
- Using the access_token retrieved from (2) attempt an introspection request to the introspection_endpoint. The request should be rejected
- Using the id_token retrieved from (2) attempt an introspection request to the introspection_endpoint. The request should be rejected
- 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
|
| Inputs | Established 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
|