Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Concurrent consent support and cdr_arrangement_id #632

Closed
nils-work opened this issue Feb 8, 2024 · 4 comments
Closed

Concurrent consent support and cdr_arrangement_id #632

nils-work opened this issue Feb 8, 2024 · 4 comments
Assignees
@nils-work
Labels
Non-breaking change A change that is not expected to result in a new endpoint version. Proposal made The DSB has proposed a specific change to the standards to address the change request Security Change or question related to the information security profile
Milestone
v1.30.0

Comments

@nils-work
Copy link
Member

nils-work commented Feb 8, 2024 •
edited
Loading

Description

The following lines are from the Security Profile > Identifiers and Subject Types section -

A Data Holder MUST only return the cdr_arrangement_id in the Token and Token Introspection End Point responses if they also support concurrent consent. This ensures that Data Recipient Software Products have a reliable way to determine whether a given Data Holder supports concurrent consent.

For any existing consents, Data Holders MUST retrospectively generate a cdr_arrangement_id such that Data Recipient Software Products can obtain a valid cdr_arrangement_id for all active consents they hold.

Area Affected

Security Profile > Identifiers and Subject Types section, under CDR Arrangement ID and Obtaining a CDR Arrangement ID.

Change Proposed

To remove these obsolete lines, as -

  1. the obligation date for supporting concurrent consent has passed (1 November 2020), meaning it must be supported by all Data Holders,
  2. the cdr_arrangement_id must always be returned in the Token and Token Introspection responses,
  3. it is not anticipated that Data Holders will have any existing, or create new consents without a cdr_arrangement_id,
  4. these statements may cause confusion by remaining in the Standards.

DSB Proposed Solution

The proposed solution can be found through the staging link provided in this comment.
@nils-work nils-work added the Security Change or question related to the information security profile label Feb 8, 2024
@nils-work nils-work added the Non-breaking change A change that is not expected to result in a new endpoint version. label Mar 6, 2024
@nils-work nils-work moved this from Full Backlog to Iteration Candidates in Data Standards Maintenance Mar 8, 2024
@nils-work
Copy link
Member Author

This issue was discussed on the 6 March Maintenance Iteration call and no objections were raised in regard to the Change Proposed.

Please add a comment if there are any concerns.

@nils-work nils-work moved this from Iteration Candidates to In Progress: Design in Data Standards Maintenance Mar 12, 2024
@nils-work nils-work self-assigned this Mar 17, 2024
@nils-work nils-work added this to the v1.30.0 milestone Mar 17, 2024
nils-work added a commit to ConsumerDataStandardsAustralia/standards-staging that referenced this issue Mar 18, 2024
@nils-work
Removed two outdated statements
3145e71 
Addresses: ConsumerDataStandardsAustralia/standards-maintenance#632
@nils-work
Copy link
Member Author

This change has been staged for review here -
ConsumerDataStandardsAustralia/standards-staging@3145e71#diff-f3adc2f53e36ac8a4dcd5b3f07910489680bfff9db6fbde092b5cd93e53ad5d0

@nils-work nils-work moved this from In Progress: Design to In Progress: Staging in Data Standards Maintenance Mar 18, 2024
@CDR-API-Stream CDR-API-Stream mentioned this issue Mar 18, 2024
Closed
@nils-work nils-work added the Proposal made The DSB has proposed a specific change to the standards to address the change request label Mar 19, 2024
@nils-work
Copy link
Member Author

This issue was raised in the agenda for the 20th March Maintenance Iteration call and there was no opposition to the change proposed, which has been staged.

@nils-work nils-work mentioned this issue Mar 26, 2024
Merged
@nils-work nils-work moved this from In Progress: Staging to Awaiting Chair Approval in Data Standards Maintenance Apr 16, 2024
JamesMBligh added a commit to ConsumerDataStandardsAustralia/standards that referenced this issue Apr 24, 2024
@JamesMBligh @nils-work
@HemangCDR @markverstege
Release/1.30.0 (#349)
43e5d04 
* 1.30.0 branch

* Updates to base build

* Update releasenotes.1.30.0.html.md

* Updated release notes templates

* Corrected typo in Description

Addresses: ConsumerDataStandardsAustralia/standards-staging#361

* Updated links

Addresses: ConsumerDataStandardsAustralia/standards-staging#362

* Updated Principles text for CX

Addresses: ConsumerDataStandardsAustralia/standards-staging#370

* Improved wrapping for long lines

Addresses: ConsumerDataStandardsAustralia/standards-staging#371

* Adding version delta and release notes

* Updates to 'Revoking consent' Standards

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#631

* Removed two outdated statements

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#632

* Corrected typo in `cdr_arragement_id`

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment)

* Changed 'Software Package' to 'Software Product'

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment)

* Updated documentation to include link

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment)

* Clarified documentation

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment)

* Updated Non-normative Example

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment)

* Clarified Register endpoint responses

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment)

* Applied change to Register API in NBL Candidate

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#629 (comment)

* Template code change

Change log and version delta details TBC.
Addresses: ConsumerDataStandardsAustralia/standards-staging#376

* Removed unused Format column

* Updated template and schema mapping

Addresses: ConsumerDataStandardsAustralia/standards-staging#376

* Removed outdated statements and examples

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#543

* Fixed typo

Addresses: ConsumerDataStandardsAustralia/standards-staging#388

* Updated date format

Addresses: ConsumerDataStandardsAustralia/standards-staging#310

* Updated based on feedback in MI18

Addresses: ConsumerDataStandardsAustralia/standards-maintenance#543 (comment)

* Standards Maintenance Issue #624: Converted solarFeedInTariff.timeVaryingTariffs into an array. Added new mandatory displayName field to solarFeedInTariff.timeVaryingTariffs

* Standards Maintenance Issue #625: Added optional period field to various energy rate objects to help support stepped tariff calculation

* Standards Maintenance Issue #627: Made changes to EnergyPlanTariffPeriod to allow sharing of banded daily supply charges

* Standards Maintenance Issue #627: Corrected bandedDailySupplyCharges to an array. Fixed typos in FDO table

* Standards Maintenance Issue #627: Fixed typos in field descriptions

* Standards Maintenance Issue #625: Fixed typos in FDO table

* Standards Maintenance Issue #624: Fixed typos in FDO table

* Standards Maintenance Issue #624: Added new ENUM values CURRENT and VARIABLE to solarFeedInTariff.scheme

* Standards Maintenance Issue #625: Corrected diff and release notes including as part of the change

* Remove spaces causing extra lines when wrapping

* Moving the typo correction to a separate issue

* Final updates to 1.30.0

---------

Co-authored-by: Nils Berge <[email protected]>
Co-authored-by: Hemang Rathod <[email protected]>
Co-authored-by: Mark Verstege <[email protected]>
@nils-work
Copy link
Member Author

Standards version 1.30.0 was published on 24/04/2024 incorporating this change from MI18.

@github-project-automation github-project-automation bot moved this from Awaiting Chair Approval to Done in Data Standards Maintenance Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nils-work nils-work

Labels
Non-breaking change A change that is not expected to result in a new endpoint version. Proposal made The DSB has proposed a specific change to the standards to address the change request Security Change or question related to the information security profile
Projects
Data Standards Maintenance
Status: Done
Milestone
v1.30.0
Development

No branches or pull requests
1 participant
@nils-work