Skip to main content

FAPI-RW-ID2-ENSURE-CLEARTEXT-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 not unsigned (i.e., plain text JSON serialisations), and if they are, the server rejects 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 at least 2048 bits in length
  7. Verify JWKS contains at least one key with alg of PS256 or ES256
  8. Create authorisation request with content 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. Serialise the authorisation request without signing it with any cryptographic signature
  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_authorisation_request_endpoint specified within the discovery document
  14. Verify the PAR endpoint returned HTTP Status 400 with an invalid_request_object error code
Inputs
Expected ResultsThe Holder must not allow assertions which do not contain a sub claim