fix: Pass the client's content type through to Veraison rather than hard-coding #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hard-coding the CCA content type. This makes the key broker neutral with respect to the attestation type, now that a Veraison issue with parameter quoting has been resolved. Signed-off-by: Paul Howard <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The EAT/CCA content type was being hard-coded in the key broker, but this is no longer necessary because an integration issue on the Veraison side has since been resolved. We can now directly pass the content type from the attester all the way through to Veraison, which makes the key broker neutral in the negotiation.
Signed-off-by: Paul Howard [email protected]