-
Notifications
You must be signed in to change notification settings - Fork 9
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.
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
Documentation improvement: JWT Signature verification requirements during the DCR flows #442
Comments
Does the CTS support ES256 signed DCR requests yet? If not it will be difficult to formally document these requirements because the Regulators own toolset would have a 100% failure rate of otherwise compliant parties. |
This change was incorporated into release v1.15.0. Refer to Decision 212 for further details. |
@perlboy I'll leave this ticket open for the CTS team to provide a response to your inquiry |
Thank you for your query @perlboy. ACCC confirms that CTS does support ES256 signed DCR requests. |
Does this include testing whether Data Recipients properly support ES256 for all operations? |
This issue has been raised to track CDR Register issue 186 through the standards maintenance process.
Please refer to CDR Register issue 186 for details
The text was updated successfully, but these errors were encountered: