Trust registry reference
A trust registry connects the gateway to an external authority that determines which agents and issuers are trusted to interact with your surfaces. When a surface receives a request, the gateway queries the assigned registry over a DIDComm connection to check whether the caller’s DID is recognised by that authority.
Use this page to add a registry, monitor its connection state, and confirm reachability before assigning it to a surface.
For conceptual background, see Trust registries.
Fields
| Field | Editable | Description |
|---|---|---|
| Name | Yes | Human-readable display name. Appears in Issuer configuration and logs. |
| Description | Yes | Optional description of the trust registry’s purpose or governance framework. |
| OOB URL | No | The OOB invitation URL provided by the trust registry administrator. Used to establish the initial DIDComm connection. Set at creation. |
| DID Method | No | The DID method used to generate the per-registry identity. Options: Web (did:web), WebVH (did:webvh), or Peer (did:peer). Defaults to Web (did:web). Set at creation and cannot be changed. |
| Our DID | No | The gateway’s per-registry DID, created during the OOB handshake. This is the DID the trust registry uses to identify this gateway. Populated after the handshake completes. |
| Registry DID | No | The trust registry’s DIDComm identity, discovered during the OOB handshake. |
| Main DID | No | The canonical DID of the trust registry. This is the DID that agents reference in their trust-registry extensions (trust_registry_did field). Populated from the OOB invitation. |
| Connection Status | No | Current connection state. See Connection statuses. |
| Status | No | active or disabled. Disabled registries are excluded from Issuer configuration. Not editable from the dashboard; deleting a registry removes the record rather than disabling it. |
The backend also tracks a Mediator URL, the mediator endpoint auto-discovered from the OOB invitation, but it is not rendered anywhere on this page.
Besides records, the gateway publishes human-readable names to a connected registry as reference fields: the names of the Issuers registered with it and their Authorities, and the surface names of managed agents that a Trust Recorder records into it. See How names reach the trust registry.
Connection statuses
| Status | Meaning |
|---|---|
| CONNECTING | The OOB handshake is in progress. |
| AWAITING APPROVAL | Setup message sent. Waiting for the trust registry administrator to approve. |
| CONNECTED | Connection is established. TRQP queries can be issued. |
| DISCONNECTED | Previously connected. Use Reconnect to re-establish. |
| FAILED | Connection failed. Use Reconnect to retry. |
Actions
| Action | Available when | Description |
|---|---|---|
| Reconnect | Status is DISCONNECTED or FAILED. | Re-initiates the DIDComm handshake using the stored OOB URL. |
| Heartbeat icon (tooltip: Heartbeat) | Status is CONNECTED. | Sends a test query to confirm the connection is live. Returns Ping to "<name>" successful (<ms>ms) on success. |
Related
- Agent validation via Trust Registry: Configure Trust Check queries and enforce access decisions using a connected trust registry.
- Trust registries: Conceptual background.
Glad to hear it. Thanks for letting us know.
Sorry to hear that. Thanks for letting us know.