search

decentralized-identity / confidential-storage

Confidential Storage Specification and Implementation
https://identity.foundation/confidential-storage/
Apache License 2.0
79 stars 23 forks source link

Enable Async Credential Requests with Identifiers #13

Closed TelegramSam closed 4 years ago

TelegramSam commented 6 years ago

== intended as a discussion issue ==

Many Credential Request will be fulfilled asynchronously. In order to correlate requests with responses, passing identifiers along with requests and responses is useful.

Two Identifiers are useful here: one meaningful to the entity sending the request, and one meaningful to the entity fulfilling the request. A hub processing a request should preserve and return the originator's identifier. The hub will also generate an id of its own to track the request.

we can use the 'identifier' attribute, but I worry about the confusion between the requester id and the hub id for the request.

On the topic of responses: ReceiveAction is the reciprocal of SendAction. Should that be the response?

If we will use the Messages endpoint for polling for status, we'll need an action for that.

Actions also can have an actionStatus, of ActionStatusType. Valid options include ActiveActionStatus, CompletedActionStatus, FailedActionStatus

OR13 commented 4 years ago

@TelegramSam you are assigned this issue, I'm pretty sure we are a ways out from being able to address it, given our current layering approach. Feel free to close, or dig at my or @dlongley @csuwildcat for better answers to these.

OR13 commented 4 years ago

Group agreed out of scope.