Skip to main content
Trust Sources

Update trust source

PATCH/v4/config/ows/trust/sources/{trustSourceId}

Changes one trust source of the organisation. The change is partial: a member that you leave out keeps its stored value.

  • enabled: false turns the source off. enabled: true turns it on again.
  • usedFor replaces the one role of the source.
  • A new url or signerCertificates of a list makes the wallet read the list again in the request, with the rule of the add. A list that cannot be used gives 400 with errorId trust_source.list_not_usable (The list cannot be used: <reason>; the reason is the HTTP status, the read failure or the signature failure), and nothing changes. A change of the usedFor of a list to status_issuer also reads the list again, because the list must have a service that gives this role. Another change that keeps the URL and the signer certificates does not read the list.
  • A source in use cannot be turned off and cannot change its url or its usedFor: the answer is 400 (trust_source.in_use). Read trust source usage tells where it is used.
  • certificates replaces the CA certificates of a trust anchor.

url and signerCertificates are refused for a trust anchor, and certificates for a list. API key scope: trust-sources:update (the older trust-anchors:update still works for a period).

Authorizations

  • Authorizationstringheaderrequired

    Your API key with the prefix ApiKey: ApiKey <your-api-key>. Get an API key.

    Scope:trust-sources:update

Path parameters

  • trustSourceIdstring<uuid>required

    The id of a trust source of the organisation, from List trust sources. A value that is not a UUID gives HTTP 404, as an unknown ID.

    Example:"6d2c0b8e-3f4a-4c1d-9e2b-7a5f1c3d8e90"

Body

application/json

The members to change. A member that the operation does not declare is refused (<name>: unknown field).

  • namestring

    New name. A name of only spaces keeps the stored name.

    Example:"EU wallet providers"

  • enabledboolean

    false turns the source off. A source in use cannot be turned off (trust_source.in_use). true turns it on again.

    Example:false

  • usedForenum<string>

    The new role that the organisation uses the source for. A source in use cannot change it (trust_source.in_use).

    Available options:wallet_provider,pid_provider,qeaa_provider,pub_eaa_provider,eaa_provider,mdl_issuer,status_issuer,access_certificate_provider,registration_certificate_provider

    Example:"wallet_provider"

  • urlstring

    New https URL of a list, at most 2048 characters. The wallet downloads the list again in the request. A source in use cannot change it (trust_source.in_use).

  • certificatesstring

    New CA certificates (and optional CRLs) of a trust anchor, as PEM text, with the rules of the add operation.

  • signerCertificatesstring

    New certificates that sign the list, as PEM text. The wallet reads the list again in the request.

Response

application/json

The changed trust source.

  • trustSourceobject

    A trust source of the organisation (or of the sandbox organisation): CA certificates that the organisation gives (a trust anchor) or a published list that the wallet downloads. A trusted list check of the issuer, the verifier or the holder reads only the trust sources in the accepted list of its setting.