| Steps | - 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
- 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
- Retrieve the registration_endpoint from the Holder OIDC document
- Sign the DCR from (2) using the ADRβs JWKS
- Submit a POST request to the registration_endpoint
- The Holder should reject the registration request due to missing token_endpoint_auth_signing_alg
- Add token_endpoint_auth_signing_alg to the DCR created at (2). Perform steps (3) β (5)
- 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
- Attempt to execute (2) β (8) again, the request should be rejected on the basis of an existing registration for the software product
- Retrieve a token from the Holder using client_credentials and private_key_jwt assertion type combined with the recently registered client_id.
- Submit a DELETE to the registration_endpoint/client_id containing the token retrieved in (10) and expect a 204 HTTP response
- Retrieve a fresh SSA (1) and construct a new DCR (2) and additional attributes (6)
- Append to the DCR the following additional fields:
- Execute (3), (4), (8) using DCR from (12) and expect a failure during registration due to invalid redirect_uris
- Update the DCR in (12) to specify a subset of the redirect_uris from the SSA
- Execute (13) using DCR from (14) and expect a successful client_id with a token
- Construct a DCR Update request using a modified subset of redirect_uris from the SSA (which should be retrieved again from the Register)
- Use the token retrieved in (9) to submit a PUT to the registration_endpoint/client_id, the details should be updated by the Holder
- Attempt to perform GET registration_endpoint/client_id using an Authorization header of Bearer invalid-token-should-not-pass and expect an access denied
- Attempt to perform a client assertion as per (8) but specifying an invalid client_id, the request should be rejected
|