Skip to main content

FAPI-RW-ID2-ENSURE-INVALID-SIGNING-FAILS-PAR

NameEnsure the holder does not accept request objects which are not signed
CategoryINFOSEC
Execution MethodAUTOMATED (FAPI BASELINE)
Preconditions
DescriptionThis test verifies that request objects submitted to the PAR endpoint are suitably verified based on their cryptographic signature. If an invalid signature is detected the server should reject the request during PAR setup
Steps
  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 with PS256
  11. Replace the last 10 characters of the JWS from (9) with random alpha characters
  12. Create a client assertion containing iss, sub, jti, iat, exp and aud
  13. Sign the client assertion using PS256
  14. Dispatch the authorisation request (9) using the client assertion (11) to the pushed_authorization_request_endpoint specified within the discovery document
  15. Verify the PAR endpoint returned HTTP Status 400 with an invalid_request_object error code
Inputs
Expected ResultsThe Holder must reject requests which do not pass signature verification