Skip to main content

FAPI-RW-ID2-PAR-REJECT-AUTHORIZE-AUDIENCE

NameEnsure the holder does not accept request objects which are not signed
CategoryINFOSEC
Execution MethodAUTOMATED (FAPI BASELINE)
Preconditions
Description

This 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. These steps are conducted using the first Client registered to the Holder and occur using Client 1’s MTLS certificate.
  2. Retrieve Discovery Document and parse required endpoints
  3. Retrieve JWKS Key Set using jwks_uri attribute
  4. Validate JWKS keys are valid JSON, contain the required fields and are correctly encoded using unpadded base64url
  5. Verify all JWKS keys contain kids
  6. Verify all JWKS keys do not contain any private or symmetric keys
  7. Verify all JWKS keys are of at least 2048 bit in length
  8. Verify JWKS contains at least one key with alg of PS256 or ES256
  9. Create authorisation request with content of (roughly) similar to the following where the aud is set to the discovered authorization url:
  10. {
      "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"
    }
  11. Sign the authorisation request using PS256
  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. The PAR endpoint must respond with a HTTP Status 400 code containing an OAuth2 invalid_request_object error
Inputs
Expected ResultsThe Holder must not allow PAR requests where the request object uses the /authorise endpoint as the audience