Skip to main content

FAPI-RW-ID2-PAR-ATTEMPT-REUSE-REQUEST_URI

NameVerifies that Request URI cannot be reused
CategoryINFOSEC
Execution MethodAUTOMATED (FAPI BASELINE)
Preconditions
Description

This test tries to use a request_uri twice and expects the authorization server either show an error or redirect back with an invalid_request_uri error, PAR section 7.3 states 'the AS SHOULD make the request URIs one-time use'. If the authentication succeeds a warning will be issued.

Steps

These steps are conducted using the first Client registered to the Holder and occur using Client 1’s MTLS certificate.

  1. Retrieve Discovery Document and parse required endpoints
  2. Retrieve JWKS Key Set using jwks_uri attribute
  3. Validate JWKS keys are valid JSON, contain the required fields and are correctly encoded using unpadded base64url
  4. Verify all JWKS keys contain kids
  5. Verify all JWKS keys do not contain any private or symmetric keys
  6. Verify all JWKS keys are of at least 2048 bit in length
  7. Verify JWKS contains at least one key with alg of PS256 or ES256
  8. Create authorisation request with content of (roughly) similar to:
  9. {
      "aud": "https://localmachine:8103/local-conformance-holder",
      "scope": "openid profile bank:accounts.basic:read bank:accounts.detail:read",
      "claims": {
          "sharing_duration": 7776000,
          "id_token": {
              "acr": {
                  "value": "urn:cds.au:cdr:2",
                  "essential": true
              }
          }
      },
      "iss": "4unxLnjKSMQCTRYU1X1Bed",
      "response_type": "code id_token",
      "redirect_uri": "https://localhost.emobix.co.uk:8443/test/a/wikkitgate/callback",
      "state": "LwI4CZHGDm",
      "exp": 1603332124,
      "nonce": "vVqWbuseiL",
      "client_id": "4unxLnjKSMQCTRYU1X1Bed"
    }
  10. Sign the authorisation request using PS256
  11. Create a client assertion containing iss, sub, jti, iat, exp, and aud
  12. Sign the client assertion using PS256
  13. Dispatch the authorisation request (9) using the client assertion (11) to the pushed_authorization_request_endpoint specified within the discovery document
  14. Verify that the PAR endpoint returns HTTP Status 201 with a valid request_uri returned
  15. Verify that the content of the request uri meets entropy of at least 128-bits
  16. Initiate a browser initiation to the authorize endpoint specifying:
    • request_uri retrieved in (13)
    • client_id matching the iss of the authorisation request
    • redirect_uri matching the authorisation request
    • scope specifying scopes matching the authorisation request
    • response_type of code id_token
  17. The authorisation flow should initiate
  18. Execute (15) again using the same request_uri retrieved in (13)
  19. The authorisation flow should fail to initiate and produce invalid_request_uri error. If it succeeds this test case result is a warning.
Inputs
Expected ResultsThe Holder should not allow request uri’s to be reused.