feat(lead verifier): verification API support #376
Conversation
This file contains hidden or 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
thomas-fossati
force-pushed
the
leadverifier-368
branch
from
07254ac to
242e420
Compare
Add transparent support for the "lead verifier" mode where the usual challenge-response API accepts verification requests for composite evidence and dispatches them to the CE handler endpoint in VTS. The existing verification API logic is extended to: 1. Advertise collection types during content negotiation, as well as via the discovery interface. 2. Recognise requests for collection types that do not have an associated scheme plugin, and forward them to the CE handler. Signed-off-by: Thomas Fossati <thomas.fossati@linaro.org>
thomas-fossati
force-pushed
the
leadverifier-368
branch
from
242e420 to
c2da15a
Compare
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.
Add transparent support for the "lead verifier" mode where the usual challenge-response API accepts verification requests for composite evidence and dispatches them to the CE handler endpoint in VTS.
The existing verification API logic is extended to:
Fix #368