WebVH Hosting management

Day-to-day tasks for your WebVH Hosting appliance: create, update, name, and delete the DIDs it hosts, add DIDComm endpoints, and troubleshoot resolution.

Every service, tenant, or agent you onboard needs its own did:webvh identifier, and each one must stay resolvable and current as its keys and endpoints change. These guides cover the pnm did-mgmt commands that create, update, name, and delete hosted DIDs through your VTA, make them reachable over DIDComm, and fix resolution problems. Create and manage DIDs →

Prerequisites: an activated appliance registered with your VTA, and the pnm CLI connected to that VTA. If you have not done this yet, start with Create your first hosted DID.

Create and manage DIDs→

Create, inspect, update, and delete did:webvh identifiers on your WebVH Hosting appliance using the PNM CLI.

Give a DID a human-readable name→

Bind a short agent name such as alice to a hosted did:webvh identifier, so /@alice on your appliance redirects to the DID, and park, re-enable, or release the name later.

Make a DID reachable over DIDComm→

Add your mediator as a DIDComm service endpoint to a new or existing hosted DID, so other parties can send it DIDComm v2.1 messages.

Troubleshoot DID resolution→

Find out why a hosted did:webvh identifier, its latest version, or its agent name does not resolve from your WebVH Hosting appliance, and fix it.