[ARCHIVE] July2020-5 Dynamic Client Registration (DCR) Errors

Note: This article has been archived. It relates to a historical event that has been resolved.

Archived Text

Summary

ADRs observed errors during the Dynamic Client Registration (DCR) process, preventing them from successfully registering with DHs until a fix was implemented.

The July 2020 test scenarios, including those that relate to DCR, are available here: 

https://www.accc.gov.au/focus-areas/consumer-data-right-cdr-0/cdr-phase-1-test-scenarios-july-2020 

Participants involved	ADR & DH
Workaround	None

Occurrence A

The POST request made by the ADR to the DH registration end-point resulted in a 503 error response. The DH resolved this issue with a configuration fix.

Impact

Client registration (connectivity) not possible.

Occurrence B

ADR call to Get a client registration from a DH returned an error saying "invalid clientId“. The DH resolved this issue with a configuration fix.

Impact

Client registration (connectivity) not possible.

Occurrence C

DH request to ADR during DCR blocked by cloud platform firewall of ADR. Resolved by ADR updating the firewall rule so that requests from the DH were no longer blocked.

Impact

Client registration (connectivity) not possible.

Occurrence D

ADR received an encrypted ID token from a DH, as expected, but was unable to decrypt the ID token because the DH used an encryption key that the ADR cannot find. A fix was implemented by the DH but further details of the fix are not known.

Impact

Unable to create a consent.