Skip to main content

INFOSEC-CDR-DETAIL-SCOPES-REQUIRES-BASIC

NameEnsure that the Holder rejects Detailed requests without Basic included
CategoryINFOSEC
Execution MethodAUTOMATED (FAPI BASELINE)
Preconditions
Description

This test verifies that when a Holder is presented a list of scopes containing one of the detail scopes that the basic scope is included as well.
This test has been removed following clarification from Requirement for Basic and Detailed Scopes

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, paying attention to scope definition specifying detail but not basic:
    {
    "aud": "https:\/\/localmachine:8103\/local-conformance-holder",
    "scope": "openid profile 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. Sign the authorisation request using PS256
  10. Create a client assertion containing iss, sub, jti , iat, exp and aud
  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 400 with an oauth2 error of invalid_request

Inputs
Expected ResultsThe Holder must reject requests which specify a detail scope without specifying the matching basic scope