Skip to main content

INFOSEC-CDR-DISCOVERY-CAPABILITIES

NameVerify CDR Discovery Document
CategoryINFOSEC
Execution MethodAUTOMATED (FAPI BASELINE)
Preconditions
Description

In this particular test we verify that the discovery document does not โ€œover advertiseโ€ capability that the CDR alters further

Steps
  1. Retrieve discovery document from .well-known/openid-configuration
  2. Parse discovery document
  3. Verify id_token_signing_alg_values_supported does not contain ES256
  4. Verify token_endpoint_auth_methods_supported does not contain tls_client_auth
  5. Verify token_endpoint_auth_signing_alg_values_supported does not contain ES256
  6. Verify userinfo_signing_alg_values_supported does not contain ES256
  7. Verify request_object_signing_alg_values_supported does not contain ES256
  8. Verify that grant_types_supported contains client_credentials, refresh_token and authorization_code
  9. Verify that scopes_supported contains the following scopes as per CDR Standards:
    "bank:accounts.basic:read",
    "bank:accounts.detail:read",
    "bank:payees:read",
    "openid",
    "bank:transactions:read",
    "common:customer.detail:read",
    "profile",
    "cdr:registration",
    "common:customer.basic:read",
    "bank:regular_payments:read"
Inputs
Expected Results
  • The Holder is not advertising an ES256 algorithm availability for anything
  • The Holder is not advertising tls_client_auth for authentication method
  • The Holder is advertising the required CDR scopes