Skip to main content

FAPI-RW-ID2-PAR-TEST-PAR-AUDIENCE-ASSERTION

NameVerifies that the Holder accepts a client assertion with a PAR audience
CategoryINFOSEC
Execution MethodAUTOMATED (FAPI BASELINE)
Preconditions
Description

This test tries to use the pushed authorisation endpoint URL as the audience for Client JWT Assertion. The authorisation server is expected to accept it.

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 authorization 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",
      "state": "LwI4CZHGDm",
      "exp": 1603332124,
      "nonce": "vVqWbuseiL",
      "client_id": "4unxLnjKSMQCTRYU1X1Bed"
    }
  9. Create a client assertion containing iss, sub, jti, iat, and exp
  10. Set the client assertion aud attribute to the PAR endpoint URL
  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. Verify that the PAR endpoint returns HTTP Status 201 with a valid request_uri returned
Inputs
Expected ResultsThe Holder must accept PAR requests with the PAR URL as the audience