-
Notifications
You must be signed in to change notification settings - Fork 8
Open
Description
Summary
The PR #29 introduced the first stage of support for the CoSERV request-response API, but it is limited to unsigned output from the server. This request is to enhance the API to support signed output as well.
Detail
- The
coserv::QueryRunnertype currently offers theexecute_query_unsigned()method. The request is basically to introduce a new method alongside that calledexecute_query_signed(), which essentially does the same job, but sets the media type asapplication/coserv+coseinstead ofapplication/coserv+cbor. This will trigger the server to produce signed rather than unsigned output. - There is a dependency on signed CoSERV support being added to the
coserv-rscrate. - There's a design question to decide who verifies the signature - should verification be bundled into the client library, or do we make that the caller's problem?
Metadata
Metadata
Assignees
Labels
No labels