Subscribing to Trust Lists

Overview

Procivis One enables you to subscribe to different kinds of trust lists and resolve trust information during interactions. Refer to the Standards for the latest list of supported trust list standards.

The workflow for subscribing to trust lists:

1. Create a trust collection

2. Add a trust list (or list of lists) to a collection

note

Subscribing to a trust list is not the same as enforcing the trust list. See Ecosystem Enforcement.

Creating a collection

A trust collection is a container for trust subscriptions.

POST /api/trust-collection/v1
Content-Type: application/json
Accept: application/json
Authorization: Bearer <TOKEN>

{
  "name": "Trust Collection",
  "ecosystem": "EUDI",
  "organisationId": "{{ORG-UUID}}", // only needed when not using STS auth
}

• ecosystem — reference a configured instance of ecosystem. Each collection must be linked with one ecosystem. When you later use an ecosystem during an interaction, the system uses all linked trust collections for trust checks.

Returns:

{
  "id": "{{TRUST-COLLECTION-UUID}}"
}

tip

Store the returned trust collection ID for the next step.

Adding a subscription

Subscribe to a trust list by adding an entry to a trust collection.

POST /api/trust-collection/v1/{trust-collection-id}/trust-list
Content-Type: application/json
Accept: application/json
Authorization: Bearer <TOKEN>

{
  "name": "EU LoTE",
  "reference": "https://example-trust.com/list",
  "role": "PID_PROVIDER",
  "type": "LOTE_SUBSCRIBER"
}

• reference - Provide the URL where the trust list is published.
• role - For Lists of Trusted Entities (LoTE) only. Each list in a LoTE is separated by role; provide the role the list is published for. This is an enum and the options can be seen in the API schema.
• type - Reference a configured instance of trustListSubscriber. Refer to Core Config Reference - Trust list subscriber for supported types.

Returns:

{
  "id": "{{TRUST-ENTRY-UUID}}"
}

Resolving trust information

Once an ecosystem is applied to an interaction, trust information is resolved automatically. See how to look this up for your use case:

• Ecosystem Enforcement Reference for Issuers
• Ecosystem Enforcement Reference for Wallets
• Ecosystem Enforcement Reference for Verifiers

Sharing subscriptions

A trust list subscription applies to the subscribing organization, but can be shared in a few ways.

In server environments

In multi-tenant setups, assign a parent organization to automatically subscribe to the trust collections of the parent. Child organizations can additionally add their own subscriptions. See Organization hierarchy for details.

In wallet apps

Wallet Providers can offer a defined set of trust collections for wallet users to optionally subscribe to. Additionally, providers can enable a toggle in the wallet that lets users block all interactions with untrusted entities. See Wallet Provider Configuration for details.