Merge pull request #122 from ConsumerDataStandardsAustralia/maintenan…

…ce/460 Standards Maintenance #460
ConsumerDataStandardsAustralia · Feb 4, 2022 · e5f9a79 · e5f9a79
2 parents 53d9501 + 266f1be
commit e5f9a79
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/slate/source/includes/releasenotes/releasenotes.1.16.0.html.md b/slate/source/includes/releasenotes/releasenotes.1.16.0.html.md
@@ -31,9 +31,9 @@ This release minor errata and documentation fixes.
 
 |Change|Description|Link|
 |------|-----------|----|
+| Authentication Flows | Clarified requirements for Data Recipient Software Products S256 code challenge method | [Authentication Flows](../../#authentication-flows) |
 | Normative References | Updated the normative reference for RFC9126 to add the link to the associated standard |  [Normative References](../../#normative-references) |
 
-
 ## Consumer Experience
 
 |Change|Description|Link|

diff --git a/slate/source/includes/security/_authentication_flows.md b/slate/source/includes/security/_authentication_flows.md
@@ -39,11 +39,17 @@ No other flows are currently supported.
 *	Data Recipient Software Products **SHOULD NOT** reuse "authorization_code" values, and if reused, it will be rejected.
 * Data Recipient Software Products **MAY** send requests with a "x-fapi-customer-ip-address" header containing a valid IPv4 or IPv6 address.
 
+```diff
+Replaced the statement:
+- Data Recipient Software Products MUST use [RFC9126] (PAR) with [PKCE] (RFC7636) and, if supported, MUST use S256 as the code challenge method.
+with:
++ Data Recipient Software Products MUST use [RFC9126] (PAR) with [PKCE] (RFC7636) and MUST use S256 as the code challenge method.
+```
 
 **From September 16th 2022**, the following requirements apply in addition to the FAPI 1.0 Migration Phase 1 requirements:
 
 *	Data Recipient Software Products **MUST** support FAPI 1.0 Advanced Profile (**[FAPI-1.0-Advanced]**).
-* Data Recipient Software Products **MUST** use **[RFC9126]** (PAR) with **[PKCE]** (RFC7636) and, if supported, **MUST** use S256 as the code challenge method.
+*   Data Recipient Software Products **MUST** use **[RFC9126]** (PAR) with **[PKCE]** (RFC7636) and **MUST** use S256 as the code challenge method.
 *	Data Recipient Software Products **SHOULD** use OIDC Authorization Code Flow.
 
 <a id="hybrid-flow"></a>