[ARCHIVED] July 2021 CDR Register Design Change Management Guidance

Note: This article is out of date and has been archived.

It refers to CDR Register design changes that have been superseded and compliance dates that have passed.

Archived Text

The CDR Register design versions 1.3.0 and 1.5.0 introduce requirements for data holders which may need to be managed in preparation for their 1 July 2021 obligations. Note 1.4.0 of the CDR Register design does not introduce any changes to obligations for 1 July 2021.

This article provides guidance on how data holders are expected to ensure these requirements are met and how their interactions with the CDR Register and CTS platforms are to be coordinated. 

This table summarises the impact of each change on ecosystem entities.  Details on each change follow.

Issues	CDR Participant Portal	CDR Register	CTS	Date available to test	Data Holders	Accredited Data Recipients
sector_identifier_uri support for PPID calculations #52 and #172	✔	✔	✔	Mid-June	✔	✔
legal_entity_id and legal_entity_name added to SSA and optionally part of the registration response #141 & #172				N/A	✔
openid scope added to SSA #106			✔	Now	✔
profile scope added to SSA #173		✔	✔	Mid-June	✔
software_roles is now optionally part of the registration response #84				Now	✔
request_object_signing_alg is now required as part of the registration response #79		✔	✔	Mid-June	✔

Github Issue #52 and #172

sector_identifier_uri support for PPID calculations

Data holders are expected to support the sector_identifier_uri field from 01 July 2021.

Please refer to the CDR Register Design Reference Client Registration section for specification.

Further guidance on Data Holder sector_identifier_uri Support has been published on the CDR Support Portal

Data holders will be expected to perform their own quality assurance activities to ensure support of the sector_identifier_uri

The CTS is currently testing sector_identifier_uri test cases. Those data holders who have already completed CTS are encouraged to complete the latest CTS test plan against their solutions if sector_identifier_uri support testing has not been conducted.

The CDR Participant Portal and the CDR Register will be releasing functionality for data recipients to configure the sector_identifier_uri in the participant portal prior to 1 July 2021.  ACCC will notify participant when this is available.

ADRs can then leverage sector identifier functionality with data holders from 1 July 2021 onward.

Github Issues #141 and #172

legal_entity_id and legal_entity_name are added to SSA and optionally part of the registration response

This issue should only impact data holders who have chosen to persist these values. Data holders will be expected to perform their own quality assurance activities to ensure if they return legal_entity_id and legal_entity_name fields as part of the RegistrationProperties schema, the field is populated as per specification.

This issue is out of scope for CTS testing

Github Issue #106

openid scope added to SSA

The CTS is currently testing openid scope support in its test cases. Those participants who have not tested this functionality through the CTS will be required to perform their own quality assurance activities to ensure client registration flows will be supported with the openid scope.

Those data holders who have already completed CTS are encouraged to complete the latest CTS test plan against their solutions if openid scope testing has not been conducted.

Github Issue #173

profile scope added to SSA

The CTS is expected to support profile scope test cases by mid-June 2021. Participants will be required to perform their own quality assurance activities to ensure client registration flows will be supported with the profile scope.

Data holders are encouraged to complete the latest CTS test plan against their solutions once the mid-June profile scope testing is available.

Github Issue #84

software_roles is now optionally part of the registration response

This change should have no impact to data holders who have not chosen to persist this value.

Data holders will be expected to perform their own quality assurance activities to ensure if they return the software_roles field as part of the RegistrationProperties schema, the field is populated as per specification.

This issue is out of scope for CTS testing

Github Issue #79

request_object_signing_alg is now required as part of the registration response

Data holders will now be required to return request_object_signing_alg as part of the registration response. Our impact assessment has indicated that data holders are already returning this value.

The CTS is expected to support request_object_signing_alg  test cases by mid-June 2021

Data holders will be required to perform their own quality assurance activities to ensure client registration flows will return the request_object_signing_alg  field.

Data holders are encouraged to complete the latest CTS test plan against their solutions once the mid-June test plan is available.