Updated identifiers

Moved pre-requisite note for registration to SSA section Updated the guidance on SSAs Removed the July 2021 references Brought in the SSA table directly Added reference to sector_identifier_uri in sub section Replaced references to [RFC7519] with [JWT] Added RFC7519 to normative standards as [DCR] and updated references Added comments about registration section Updated comments on participant statuses to be more definitive Removed sections of participant status that are covered or should be moved to guidance
ConsumerDataStandardsAustralia · Oct 17, 2021 · 1dbba1b · 1dbba1b
1 parent c6cdf54
commit 1dbba1b
Show file tree

Hide file tree

Showing 8 changed files with 83 additions and 640 deletions.
diff --git a/slate/source/includes/register/_clientRegistration.md.erb b/slate/source/includes/register/_clientRegistration.md.erb
diff --git a/slate/source/includes/register/partials/dcr/_dcr_20201101.md.erb b/slate/source/includes/register/partials/dcr/_dcr_20201101.md.erb
diff --git a/slate/source/includes/register/partials/dcr/_dcr_20210701.md.erb b/slate/source/includes/register/partials/dcr/_dcr_20210701.md.erb
diff --git a/slate/source/includes/security/_client_authentication.md b/slate/source/includes/security/_client_authentication.md
@@ -155,7 +155,7 @@ token=45ghiukldjahdnhzdauz&token_type_hint=refresh_token
 }
 ```
 
-In addition to the requirements for [Self-signed JWT Client Authentication](#self-signed-jwt-client-authentication), the `client_id` is the ID of the Data Holder obtained from the CDR Register.
+In addition to the requirements for [Self-signed JWT Client Authentication](#self-signed-jwt-client-authentication), the `client_id` is the `Data Holder Brand ID` as issued by CDR Register.
 
 ### Data Recipients calling Data Holders
 
@@ -242,18 +242,6 @@ In addition to the requirements for [Private Key JWT Client Authentication](#pri
 * Refresh tokens will not be provided for grant_type `client_credentials`
 * `client_id`, `iss` and `sub` claims MUST be set to the ID of the calling client `Data Recipient Brand ID` OR `Software Product ID` issued by the CDR Register
 
-<p class="content-flagged for-removal"/>
-### Identifiers
-`client_id`, `sub` and where appropriate `iss`, are expected to contain the unique identifier for the client.<br>
-
-The following client identifiers will be used:
-
-Client | Scenario | Identifier
-:-- | :-- | :--
-**Software Product** | Calls to Data Holder Brand Authenticated APIs | `Client ID` as issued by the target Data Holder Brand<
-**Data Recipient Brand / Software Product** | Calls to [CDR Register Authenticated APIs](#consumer-data-right-cdr-register-apis) | `Data Recipient Brand ID` or `Software Product ID` as issued by CDR Register
-**Data Holder Brand** | Calls to Data Recipient [Revocation](https://consumerdatastandardsaustralia.github.io/standards/#end-points) and [CDR Arrangement Management APIs](https://consumerdatastandardsaustralia.github.io/standards/#end-points) | `Data Holder Brand ID` as issued by CDR Register
-
-*_`Data Recipient Brand ID` as a client identifier will be deprecated in a future version of the CDR Register design and is currently retained for backwards compatibility_
-
-<p class="content-flagged for-removal end"/>
+<aside class="notice">
+Note that the values of <code>Data Recipient Brand ID</code> and <code>Software Product ID</code> as the same.  <code>Data Recipient Brand ID</code> as a client identifier will be deprecated in the future and is currently retained for backwards compatibility
+</aside>