ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 20th of June 2024
When: Weekly every Thursday at 3pm-4:30pm AEDT
Location: Microsoft Teams
Meeting Details: Join on your computer, mobile app or room device Click here to join the meeting
Meeting ID: 446 019 435 001
Passcode: BU6uFg
Download Teams | Join on the web
Join with a video conferencing device
teams@vc.treasury.gov.au
Video Conference ID: 133 133 341 4
Alternate VTC instructions
Or call in (audio only)
+61 2 9161 1229,,715805177# Australia, Sydney
Phone Conference ID: 715 805 177#
Find a local number | Reset PIN
Learn More | Meeting options
- 5 min will be al lowed for participants to join the call.
We acknowledge the Traditional Custodians of the various lands on which we work today and the Aboriginal and Torres Strait Islander people participating in this call.
We pay our respects to Elders past, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.
The Consumer Data Right Implementation Calls are recorded for note taking purposes. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material shall be provided without the participant's consent. Participants may contact@consumerdatastandards.gov.au should they have any further questions or wish to have any material redacted from the record.
By participating in the Consumer Data Right Implementation Call you agree to the Community Guidelines. These guidelines intend to provide a safe and constructive space for members to discuss implementation topics with other participants and members of the ACCC and Data Standards Body.
⭐ indicates change from last week.
| Type | Updated | Links |
|---|---|---|
| Standards | Version 1.30.0 | Published: 24th of April 2024 Change log |
| Maintenance | Iteration 19 Completed | Keep an eye on Decision Proposal 347 for updates and outcomes |
| Maintenance | Iteration 19 Minutes published | 12 June 2024 Meeting Minutes |
| Maintenance ⭐ | Iteration 20 Kick-off is 10th of July 2024 |
Sign-up and Register Data Standards Body Events |
| Maintenance ⭐ | Iteration 20 Schedule: 10/07/2024 Kick-off and backlog review 24/07/2024 Consultation 7/08/2024 Consultation and new issue checkpoint 21/08/2024 Proposal Checkpoint 4/09/2024 Approvals and Documentation |
Agenda page to come |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| DSB Newsletter ⭐ | 14th of June 2024 | View in browser here |
| Consultation | Decision Proposal 229 - CDR Participant Representation | Placeholder: no close date Link to consultation |
| Consultation | Noting Paper 279 - Accessibility Improvement Plan | No Close Date Link to consultation |
| Consultation | Noting Paper 323 - NFR Workshops | Link to consultation |
| Consultation ⭐ | Noting Paper 348 - Use Case Enablement Experiment: Account Origination |
Open for comment: 12th July 2024 Link to Noting Paper |
| Consultation | Noting Paper 351 - LCCD Risk workshop summary | No feedback sought Link to Noting Paper |
| Engineering | Survey on updates to the GitHub Readmes Closes 21st of June 2024 |
Complete the survey |
| Publication | The ACCC has recently published a new fact sheet on CDR outsourcing arrangements. The fact sheet provides general information for participants on CDR outsourcing arrangements, the parties involved and their obligations under the CDR Rules. | - |
Provides a weekly update on the activities of each CDR stream and their work.
| Organisation | Stream | Member |
|---|---|---|
| DSB | Consumer Experience | Bikram |
| DSB | Standards Assessment Framework | Elizabeth |
None this week.
Questions will be received by the community via Microsoft Teams chat before the questions are opened to the floor. Participants can submit questions outside of the CDR Implementation Call to the CDR Support Portal.
In regards to topics for questions, we ask the participants on the call to consider the Community Guidelines when posing questions to the subject matter experts.
| Ticket # | Question | Answer |
|---|---|---|
| 2360 | Suppose a PAR is created with a request object that includes response_mode=jwt. Afterward, if the authorization endpoint is called and the request fails, should the dataholder send the response back to the ADR in the format of http://redirecturi?error=invalid_request&error_description=Could%20not%20fetch%20userDetails&state=6f7e8132-a4e5-4d2e-88c2-ea9cc8ef3596, or does the data holder need to encode the error response as a JWT as mentioned in https://bitbucket.org/openid/fapi/src/master/oauth-v2-jarm.md? Another point of clarification: if the PAR request object specifies response_mode=jwt, does the request to the authorization endpoint also need to include response_mode=jwt for the response to be sent as a JWT, or does the data holder need to retrieve the response_mode value from the request URI sent along with the authorization request? |
In response to your query - Question 1: should the dataholder send the response back to the ADR in the format of http://redirecturi error=invalid_request&error_description=Could%20not%20fetch%20userDetails&state=6f7e8132-a4e5-4d2e-88c2-ea9cc8ef3596, Answer 1: No, it should be a JWT as per below. Question 2: or does the data holder need to encode the error response as a JWT as mentioned in https://bitbucket.org/openid/fapi/src/master/oauth-v2-jarm.md? Answer 2: Yes Question 3: Another point of clarification: if the PAR request object specifies response_mode=jwt, does the request to the authorization endpoint also need to include response_mode=jwt for the response to be sent as a JWT, Answer 3: I don't believe that is necessary, as it has already been provided through the PAR request (also see below). Question 4: or does the data holder need to retrieve the response_mode value from the request URI sent along with the authorization request? Answer 4: I'm not sure what you mean here, but the expectation is that the details provided through the PAR request are trusted. Please let me know if you feel this is incorrect or believe the Data Standards or upstream normative specifications suggest otherwise, |
Attendees are invited to raise topics related to the Consumer Data Right that would benefit from the DSB and ACCCs' consideration.
View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |