Skip to main content

INFOSEC-CLIENT-REGISTRATION-HAPPY

NameVerifies that a Holder accepts dynamic registrations, allows deletes and updates and rejects invalid registrations
Category

INFOSEC

Execution Method

Semi AUTOMATED (VTT)

Description

In this particular test the Data Recipient attempts a Dynamic Client Registration to the Data Holder using a valid SSA and content.

Preconditions
  • The Data Recipient must not be currently registered
  • The Data Recipient must be recently added
Steps
  1. After retrieving a token from the Register IDP retrieve an SSA for the Data Recipients Software Product and populate it in the software_statement field
  2. Construct a Dynamic Client Registration request containing iss, iat, exp, jti, aud, token_endpoint_auth_method, grant_types, response_types, id_token_signed_response_alg, id_token_encrypted_response_alg, id_token_encrypted_response_enc, software_statement
  3. Retrieve the registration_endpoint from the Holder OIDC document
  4. Sign the DCR from (2) using the ADR’s JWKS
  5. Submit a POST request to the registration_endpoint
  6. The Holder should reject the registration request due to missing token_endpoint_auth_signing_alg
  7. Add token_endpoint_auth_signing_alg to the DCR created at (2). Perform steps (3) β†’ (5)
  8. The Holder should respond with a Client Registration aligned with RFC7591 and documented in the CDR Register specification and containing client_id and client_id_issued_at fields
  9. Attempt to execute (2) β†’ (8) again, the request should be rejected on the basis of an existing registration for the software product
  10. Retrieve a token from the Holder using client_credentials and private_key_jwt assertion type combined with the recently registered client_id.
  11. Submit a DELETE to the registration_endpoint/client_id containing the token retrieved in (10) and expect a 204 HTTP response
  12. Retrieve a fresh SSA (1) and construct a new DCR (2) and additional attributes (6)
  13. Append to the DCR the following additional fields:
  14. Execute (3), (4), (8) using DCR from (12) and expect a failure during registration due to invalid redirect_uris
  15. Update the DCR in (12) to specify a subset of the redirect_uris from the SSA
  16. Execute (13) using DCR from (14) and expect a successful client_id with a token
  17. Construct a DCR Update request using a modified subset of redirect_uris from the SSA (which should be retrieved again from the Register)
  18. Use the token retrieved in (9) to submit a PUT to the registration_endpoint/client_id, the details should be updated by the Holder
  19. Attempt to perform GET registration_endpoint/client_id using an Authorization header of Bearer invalid-token-should-not-pass and expect an access denied
  20. Attempt to perform a client assertion as per (8) but specifying an invalid client_id, the request should be rejected
Inputs
  • SSA Retrieved from the Register
  • Data Recipient Details
Expected Results
  • The Recipient is able to register with baseline details
  • The Recipient is able to delete their registration
  • The Recipient is able to update their registration
  • The Recipient is able to specify redirect URIs which can be a subset from the Register SSA
  • The Holder rejects requests to update redirect URIs which are not part of the SSA
  • The Holder should accept registration requests that are missing the optional fields