Skip to main content

Enforcing an Ecosystem as a Provider

When managing remote instances as a Wallet or Verifier Provider, you can configure ecosystem enforcement and syncing of schemas and trust collections.

Prerequisites​

The provider organization must have an ecosystem enabled. See Enabling Ecosystems for instructions.

The managed instance reads the ecosystems from the provider metadata endpoints:

POST /ssi/wallet-provider/v1/{id} POST /ssi/verifier-provider/v1/{id}

Of the ecosystems selected by the provider organization, the user is able to select which ecosystems to use, and update their own instance's organization with selected ecosystems, using the same method described in Enabling Ecosystems.

Enforcing an ecosystem​

For wallets, incoming credential offers and proof requests are handled using the auto-detection process described in Enforcing an Ecosystem as a Wallet.

For verifiers, the same mechanism used by standalone verifying organizations applies: an ecosystem can be set during creation of a proof request, or required for all proof requests by setting enforceEcosystemAsVerifier. See Enforcing an Ecosystem as a Verifier.

If the provider organization has selected only one ecosystem and set enforceEcosystemAsVerifier, every managed verifier instance enforces that ecosystem automatically, without needing to separately select it.

Requiring ecosystem enforcement​

When ecosystems are enabled, any interaction which is "untrusted" according to the constraints of all selected ecosystems is still allowed by default. To only allow "trusted" interactions, update the provider organization:

PATCH /api/organisations/v1/{id}

{
  "configuration": {
    "enforceEcosystemAsHolder": true,
    "enforceEcosystemAsVerifier": true
  }
}

Set enforceEcosystemAsHolder to require trusted interactions for managed wallet instances, and enforceEcosystemAsVerifier to require trusted interactions for managed verifier instances. If you provide both types of instances, set both flags.

Trust syncing​

All trust collections are associated with one ecosystem. When the provider creates trust collections and subscribes to trust lists and anchors, these collections are automatically synced to any registered instance which also has enabled the same ecosystem.

Schemas syncing​

Credential schemas and proof schemas can be associated with an ecosystem. This is a Provider-only action: tagging a schema with an ecosystem enables it to be automatically synced to any managed instance that has also selected that ecosystem. Schema syncing and ecosystem enforcement are independent — associating a schema with an ecosystem does not itself enforce anything.

To associate a credential schema with an ecosystem, use ecosystem during its creation.

POST /api/credential-schema/v2

{
  {{...}}
  "ecosystem": "EUDI"
}

A successful call returns 201.