Make DidManagementApi
more explicit
#220
Labels
api
breaking-change
Will require manual intervention for version update
enhancement
New feature or request
Feature Request
The
DidManagementApi
will undergo the following changes:publish
andunpublish
serviceEndpoints
:PATCH /dids/endpoint
: body contains the DID and the service endpoint to replace. Returns a 400 if the endpoint does not exist existsDELETE /dids/endpoint
: body contains the DID and the service endpoint ID to remove. Returns a 400 if the endpoint does not exist.POST /dids/endpoint
: body contains the DID and the service endpoint ro add. Returns a 409 if the same endpoint already exists.Which Areas Would Be Affected?
DID management API
Why Is the Feature Desired?
DIDs are managed items, the are a mere representation of a participant, so modifying them directly should not be possible. The "single source of truth" must
always be the
DidResource
which we hold in the database.More specific endpoints, avoid the danger of completely overwriting a DID.
Solution Proposal
If possible, provide a (brief!) solution proposal.
The text was updated successfully, but these errors were encountered: