Skip to content

Commit

Permalink
Release/1.24.0 (#304)
Browse files Browse the repository at this point in the history 
* Standards Maintenance Issue 546: Updated DCR and Register swagger specifications to use Common Field Types

* Added diff and release notes

* Fixed redirect_uris array use of URIString in relation to maintenance comment: ConsumerDataStandardsAustralia/standards-maintenance#546 (comment)

* Updated code formatting and indenting

* Added Enum common type usage

* Updated DCR and Register specs based on community feedback to the Common Field Types implementation

* Updated swaggers to remove format fields

* Updated diff for the Register API changes

* Fixed formatting

* Updated Register APIs based on ACCC feedback

* Base branch for v1.22.0

* Draft updates 1 DP 275

* Retain v1.21.0 delta statements

* Rebuild

* Fixed open-status reversal

* Rebuild

* Create release notes
Add archive entry
Add change log entry

* Release notes

* Add archived API versions

* Add new field to the swagger
Add FDO
Update endpoint schedule

* Add diff statements

* Fix missing obselete link in Get Accounts

* Fix obselete message bug

* Fixed Issue with AccontDetail

* Rebuild
Add in Telco diff statement
Add Telco release notes

* Merge of 1.22.0

* Remove external refs on client IDs

* Remove common string references

* Review updates

* Release notes

* Rebuild
Diff statement

* Updates to x-v headers

* reverted account scope

* Updated other account scopes

* Update extended security documentation

* Rebuild

* Engage Festive

* Rebuild with FESTIVE ENGAGED

* Fix additional TDIF links

* Fix ACCC fonts

* Fix minor defects picked up after publish
Rebuild

* - Update version to 1.22.1
- Remove diff statements
- Add links for archive
- Add draft release notes

* Removed santa hat

* Restored diff overview statement
Removed last actual diff statement

* Full rebuild

* Add binding statement

* Add diff and release notes

* Fix diff typo

* Fix FDOs
Fix Obligation table
Add release notes

* Update

* Fix the binding date for Get Energy Account Detail V2
Removed the TBC dates for v1.19.0
Release notes

* Rebuild

* Update end point version schedule links
Release notes

* Changed error model for energy to ResponseErrorListV2
Rebuild

* Fixed typo
Rebuild

* Update release notes for 227

* Rebuild

* Added release notes for Telco

* Apply energy changes to SDH swagger also

* Rebuild

* Fix error model in Telco
Fix release note types
Rebuild

* Update V2 error list (#267)

* Fix Telco merge
Rebuild

* Rebuild

* Fix publish date
Rebuild

* Base branch for 1.23.0

* Standards Maintenance Issue #576: Update security profile sections allowing ID token encryption when using ACF

* Updated DCR spec to treat ID token encryption claims as conditional

* Standards Maintenance Issue #576: Removed Additional Note for v1.22.0 from version delta notes

* Rebuild

* Rebuild

* Rebuild

* Squashed 1.23.0 changes

* Create v1.24.0 branch

* Remove errant diff statements

* Rebuild

* Prepare v1.24.0

* Standards Maintenance Issue #565: Updated wording and corrected a typo in the 'Issued by the Register CA for Data Recipients' table. Corrected a typo in the 'CDR Certificate Authority' section. Addresses comment ConsumerDataStandardsAustralia/standards-maintenance#565 (comment)

* Standards Maintenance Issue #565: Corrected spelling mistake in description of RejectionMetricsV2.unauthenticated field. Addresses comment ConsumerDataStandardsAustralia/standards-maintenance#565 (comment)

* Standards Maintenance Issue #565: Fixed description of BankingAccountDetailV3.lendingRates field. Addresses comment ConsumerDataStandardsAustralia/standards-maintenance#565 (comment)

* Standards Maintenance Issue #565: Minor corrections. Addresses comments ConsumerDataStandardsAustralia/standards-maintenance#565 (comment) and ConsumerDataStandardsAustralia/standards-maintenance#565 (comment) and ConsumerDataStandardsAustralia/standards-maintenance#565 (comment)

* Standards Maintenance 535: Updated Private Key JWT client authentication requirements

* Updated release version to 1.24.0

* Standards Maintenance Issue #565: Updated description of 'period' paramater in Get Metrics API. Addresses comment ConsumerDataStandardsAustralia/standards-maintenance#565 (comment)

* Standards Maintenance Issue #565: Updated description of 'PENSION_RECIPIENT' values in Product & Account Components section. Addresses comment ConsumerDataStandardsAustralia/standards-maintenance#565 (comment)

* Standards Maintenance Issue #565: Added statements noting CORS is not required for relevant security endpoints and Register and DCR APIs. Addresses ConsumerDataStandardsAustralia/standards-maintenance#565 (comment)

* Standards Maintenance 532: Updated Customer API to align x-fapi-auth-date definition

* Standards Maintenance Issue #565: Listed specific APIs in the 'Unattended' section. Fixed incorrect Energy API names. Addresses ConsumerDataStandardsAustralia/standards-maintenance#565 (comment)

* Standards Maintenance Issue #565: Updated description of SecondaryHolderMetrics.rejections. Addresses ConsumerDataStandardsAustralia/standards-maintenance#565 (comment)

* Corrected typos

* Standards Maintenance Issue #520: Added 'rates' object to EnergyPlanSolarFeedInTariff structure. Incremented versions of Get Generic Plan Detail and Get Energy Account Detail APIs

* Standards Maintenance Issue #520: Added archieve files for Get Energy Account Detail and Get Generic Plan Detail APIs

* Standards Maintenance Issue #565: Added actual % values represented by examples for 'RateString' field type. Addresses comment ConsumerDataStandardsAustralia/standards-maintenance#565 (comment)

* Standards Maintenance Issue #574: Added new Authorisation CX Standard for additional account selection functionality in the authorisation flow

* Corrected requirements for the Large Payload tier

* Standards Maintenance Issue #496: Removed x-fapi-interaction-id from response headers of Get Energy Plans and Get Energy Plan Details public APIs

* Standards Maintenance Issue #496: Added link to CR in release notes

* Standards Maintenance Issue #574: Added link to CR in release notes

* Standards Maintenance Issue #520: Added link to CR in release notes

* Standards Maintenance Issue #565: Added link to CR in release notes

* Standards Maintenance Issue #577: Made various changes to the Certificate Signing Request Profile table. Removed the Test Environment details from the Certificate Trust Model section

* Rebuild
Update versions
Remove date TBCs
Fixed typo in diff statement
Reordered FDOs by date

* Rebuild

* Rebuild to correctly create swagger markdown

* Update change log
Rebuild

---------

Co-authored-by: Mark Verstege <[email protected]>
Co-authored-by: Kirkycdr <[email protected]>
Co-authored-by: kirkycdr <[email protected]>
Co-authored-by: Hemang Rathod <[email protected]>
  • Loading branch information
@JamesMBligh @markverstege
@kirkycdr @HemangCDR
5 people authored May 7, 2023
1 parent 4a9e0bc commit d626374
Show file tree
Hide file tree
Showing 101 changed files with 17,758 additions and 1,254 deletions.
5 changes: 5 additions & 0 deletions docs/includes/archives
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,11 @@
</tr>
</thead><tbody>
<tr>
<td><a href='https://consumerdatastandardsaustralia.github.io/standards-archives/standards-1.23.0/'>24/04/2023</a></td>
<td>1.23.0</td>
<td><a href='https://consumerdatastandardsaustralia.github.io/standards-archives/standards-1.23.0/'>Changes arising from Decision Proposal 298</a></td>
</tr>
<tr>
<td><a href='https://consumerdatastandardsaustralia.github.io/standards-archives/standards-1.22.1/'>22/03/2023</a></td>
<td>1.22.1</td>
<td><a href='https://consumerdatastandardsaustralia.github.io/standards-archives/standards-1.22.1/'>Changes arising from Change Request 576 (Maintenance iteration 14)</a></td>
Expand Down
6 changes: 3 additions & 3 deletions docs/includes/cds_admin
View file
Original file line number Diff line number Diff line change
Expand Up @@ -226,7 +226,7 @@ This operation may only be called by the CDR Register
<td>query</td>
<td>string</td>
<td>optional</td>
<td>The period of metrics to be requested. Values can be CURRENT (meaning metrics for current day), HISTORIC (meaning metrics for previous days or months) or ALL. If absent the default is ALL.</td>
<td>The period of metrics to be requested. Values can be CURRENT (meaning metrics for current period, dependent on the metric type), HISTORIC (meaning metrics for previous period, depending on the metric type) or ALL. If absent the default is ALL.</td>
</tr>
<tr>
<td>x-v</td>
Expand Down Expand Up @@ -1551,7 +1551,7 @@ This operation may only be called by the CDR Register
<td>unauthenticated</td>
<td>object</td>
<td>mandatory</td>
<td>Rejection counts for all uauthenticated end points</td>
<td>Rejection counts for all unauthenticated end points</td>
</tr>
<tr>
<td>» currentDay</td>
Expand Down Expand Up @@ -1618,7 +1618,7 @@ This operation may only be called by the CDR Register
<td>rejections</td>
<td>object</td>
<td>mandatory</td>
<td>Number of calls resulting in a rejection due to server execution over time</td>
<td>Number of calls rejected due to traffic thresholds over time</td>
</tr>
<tr>
<td>» currentDay</td>
Expand Down
8 changes: 4 additions & 4 deletions docs/includes/cds_banking
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1626,7 +1626,7 @@ To perform this operation, you must be authenticated and authorised with the fol
<li>A reasonable date/time nominated by the data holder using internal data structures</li>
</ul></li>
<li>For transaction amounts it should be assumed that a negative value indicates a reduction of the available balance on the account while a positive value indicates an increase in the available balance on the account</li>
<li>For aggregated transactions (ie. groups of sub transactions reported as a single entry for the account) only the aggregated information, with as much consistent information accross the subsidiary transactions as possible, is required to be shared</li>
<li>For aggregated transactions (ie. groups of sub transactions reported as a single entry for the account) only the aggregated information, with as much consistent information across the subsidiary transactions as possible, is required to be shared</li>
</ul>
<h3 id='endpoint-version-6'>Endpoint Version</h3>
<table><thead>
Expand Down Expand Up @@ -8295,7 +8295,7 @@ This operation does not require authentication
<td>» lendingRates</td>
<td>[<a href="#schemacdr-banking-apibankingproductlendingratev2">BankingProductLendingRateV2</a>]</td>
<td>optional</td>
<td>Fully described deposit rates for this account based on the equivalent structure in Product Reference</td>
<td>Fully described lending rates for this account based on the equivalent structure in Product Reference</td>
</tr>
<tr>
<td>» features</td>
Expand Down Expand Up @@ -8857,7 +8857,7 @@ This operation does not require authentication
<td>crn</td>
<td>string</td>
<td>conditional</td>
<td>BPAY CRN for the transaction (if available).<br/>Where the CRN contains sensitive information, it should be masked in line with how the Data Holder currently displays account identifiers in their existing online banking channels. If the contents of the CRN match the format of a Credit Card PAN they should be masked according to the rules applicable for MaskedPANString. If the contents are are otherwise sensitive, then it should be masked using the rules applicable for the MaskedAccountString common type.</td>
<td>BPAY CRN for the transaction (if available).<br/>Where the CRN contains sensitive information, it should be masked in line with how the Data Holder currently displays account identifiers in their existing online banking channels. If the contents of the CRN match the format of a Credit Card PAN they should be masked according to the rules applicable for MaskedPANString. If the contents are otherwise sensitive, then it should be masked using the rules applicable for the MaskedAccountString common type.</td>
</tr>
<tr>
<td>apcaNumber</td>
Expand Down Expand Up @@ -9964,7 +9964,7 @@ This operation does not require authentication
<td>crn</td>
<td>string</td>
<td>conditional</td>
<td>BPAY CRN of the Biller (if available).<br/>Where the CRN contains sensitive information, it should be masked in line with how the Data Holder currently displays account identifiers in their existing online banking channels. If the contents of the CRN match the format of a Credit Card PAN they should be masked according to the rules applicable for MaskedPANString. If the contents are are otherwise sensitive, then it should be masked using the rules applicable for the MaskedAccountString common type.</td>
<td>BPAY CRN of the Biller (if available).<br/>Where the CRN contains sensitive information, it should be masked in line with how the Data Holder currently displays account identifiers in their existing online banking channels. If the contents of the CRN match the format of a Credit Card PAN they should be masked according to the rules applicable for MaskedPANString. If the contents are otherwise sensitive, then it should be masked using the rules applicable for the MaskedAccountString common type.</td>
</tr>
<tr>
<td>billerName</td>
Expand Down
4 changes: 2 additions & 2 deletions docs/includes/cds_common
View file
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,7 @@
<td>header</td>
<td>string</td>
<td>conditional</td>
<td>The time when the customer last logged in to the Data Recipient Software Product. Required for all resource calls (customer present and unattended) if the customer is currently logged. Otherwise optional where the customer has not logged in. Not to be included for unauthenticated calls.</td>
<td>The time when the customer last logged in to the Data Recipient Software Product as described in <strong><a href="#nref-FAPI-R-Draft">[FAPI-R-Draft]</a></strong>. Required for all resource calls (customer present and unattended). Not required for unauthenticated calls.</td>
</tr>
<tr>
<td>x-fapi-customer-ip-address</td>
Expand Down Expand Up @@ -327,7 +327,7 @@ To perform this operation, you must be authenticated and authorised with the fol
<td>header</td>
<td>string</td>
<td>conditional</td>
<td>The time when the customer last logged in to the Data Recipient Software Product. Required for all resource calls (customer present and unattended) if the customer is currently logged. Otherwise optional where the customer has not logged in. Not to be included for unauthenticated calls.</td>
<td>The time when the customer last logged in to the Data Recipient Software Product as described in <strong><a href="#nref-FAPI-R-Draft">[FAPI-R-Draft]</a></strong>. Required for all resource calls (customer present and unattended). Not required for unauthenticated calls.</td>
</tr>
<tr>
<td>x-fapi-customer-ip-address</td>
Expand Down
4 changes: 3 additions & 1 deletion docs/includes/cds_dcr
View file
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,9 @@
</code></pre>
<p><code>POST /register</code></p>

<p>Register a client using a CDR Register issued Software Statement Assertion.</p>
<p>Register a client using a CDR Register issued Software Statement Assertion. </p>

<p>This endpoint does not require CORS.</p>

<blockquote>
<p>Body parameter</p>
Expand Down
Loading

0 comments on commit d626374

Please sign in to comment.