Authorization Response Algs should be conditional in RegistrationProperties #620
Labels
Non-breaking change
A change that is not expected to result in a new endpoint version.
Schema
Issues related to schema.
Security
Change or question related to the information security profile
Milestone
Comments
nils-work
added
the
Security
kirkycdr
moved this from Full Backlog
to Iteration Candidates
in Data Standards Maintenance
ElizabethArnold-DSB
added
the
Non-breaking change
kirkycdr
moved this from Iteration Candidates
to In Progress: Design
in Data Standards Maintenance
|
This issue has been staged for review here: ConsumerDataStandardsAustralia/standards-staging@d14e093 |
kirkycdr
moved this from In Progress: Design
to In Progress: Staging
in Data Standards Maintenance
nils-work
moved this from In Progress: Staging
to Awaiting Chair Approval
in Data Standards Maintenance
nils-work
moved this from Awaiting Chair Approval
to Done
in Data Standards Maintenance
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The properties
authorization_signed_response_algandauthorization_encrypted_response_algare designated asoptionalproperties in the client registration response schemaRegistrationPropertiessection of the DCR API definitions. According to their descriptions they areconditional.authorization_signed_response_algThe JWS alg algorithm required for signing authorization responses. If this is specified, the response will be signed using JWS and the configured algorithm. The algorithm “none” is not allowed. Required if response_type of “code” is registered by the client.
authorization_encrypted_response_algThe JWE alg algorithm required for encrypting authorization responses. If unspecified, the default is that no encryption is performed. Required if “authorization_encrypted_response_enc” is included.
Area Affected
DCR APIs > Schema > RegistrationProperties
Change Proposed
Make
authorization_signed_response_algandauthorization_encrypted_response_algconditional.The text was updated successfully, but these errors were encountered: