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.

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

Closed
CDR-API-Stream opened this issue Nov 29, 2021 · 5 comments
Labels

Comments

@CDR-API-Stream
Copy link
Collaborator

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

@perlboy
Copy link

perlboy commented Dec 1, 2021

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.

@CDR-API-Stream
Copy link
Collaborator Author

This change was incorporated into release v1.15.0. Refer to Decision 212 for further details.

@CDR-API-Stream
Copy link
Collaborator Author

@perlboy I'll leave this ticket open for the CTS team to provide a response to your inquiry

@ACCC-CDR
Copy link

ACCC-CDR commented Jun 7, 2022

Thank you for your query @perlboy. ACCC confirms that CTS does support ES256 signed DCR requests.

@perlboy
Copy link

perlboy commented Jun 11, 2022

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

4 participants