Expand description
Client surface for DIDComm protocol management.
Spec: docs/05-design-notes/didcomm-protocol-management.md.
Phase 3 lands enable_didcomm (REST-only by nature — DIDComm is
not yet running at first-enable time). The disable / migrate /
drain-cancel / report calls — and their DIDComm transport
handlers — arrive in Phase 4 verticals.
Runtime REST service-management wire types (the symmetric
REST-side of the spec §4 surface — EnableRestRequest,
UpdateRestRequest, DisableRestRequest, RollbackRestRequest,
ServiceMutationResponse) live in services.
Modules§
- matching
- Bidirectional transport-protocol matching from advertised DID-document services.
- services
- Wire types for the runtime REST service-management surface.
Structs§
- Didcomm
Status Response - Response body for
GET /services/didcomm. - Disable
Didcomm Request - Request body for
POST /services/didcomm/disable. - Disable
Didcomm Response - Drain
Cancel Request - Request body for
POST /mediators/drain/cancel. - Drain
Cancel Response - Enable
Didcomm Conflict Body - Body returned by the server on
409 ConflictfromPOST /services/didcomm/enablewhen DIDComm is already active. - Enable
Didcomm Request - Request body for
POST /services/didcomm/enable. - Enable
Didcomm Response - Mediator
Report - Mediator
Stats - Sender
Last Seen - Update
Didcomm Request - Request body for
POST /services/didcomm/update. - Update
Didcomm Response