Skip to main content

FAPI-RW-ID2-PAR-REJECT-REQUEST_URI-IN-OBJECT

NameVerifies that a Holder rejects request_uri within the request object
CategoryINFOSEC
Execution MethodAUTOMATED (FAPI BASELINE)
Preconditions
Description

This test sends a random request_uri parameter in the authorisation request object and expects the authorisation server to return an error.

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:

    {
      "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",
      "request_uri": "urn:random-uri",
      "state": "LwI4CZHGDm",
      "exp": 1603332124,
      "nonce": "vVqWbuseiL",
      "client_id": "4unxLnjKSMQCTRYU1X1Bed"
    }
  9. Sign the authorisation request using PS256
  10. Create a client assertion containing iss, sub, jti, iat, aud, and exp
  11. Sign the client assertion using PS256
  12. Dispatch the authorisation request (9) using the client assertion (11) to the pushed_authorization_request_endpoint specified within the discovery document
  13. The PAR endpoint responds with a status 400 and an OAuth2 error of either invalid_request or invalid_request_object
Inputs
Expected ResultsThe Holder must not allow PAR requests that include a request_uri attribute within the request object