Skip to main content

Revoke Accreditation

The following steps will define how to revoke a Verifiable Accreditation as a RTAO or TAO.

Step 1 Obtain issuers-registry:write access token from the Authorisation Service to write to the Issuers Registry​

To request an issuers-registry:write access token, present a self-attestation credential to the Authorisation Service with the openid issuers-registry:write scope. No accreditation credential is required, but the DID that requests the token must have at least one accepted body in the Issuers Registry (a DID that has none can only request issuers-registry:invite).

API CALL

Follow this sequence of API calls to request a issuers-registry:write access token:

  • GET DCQL query: Begin by fetching the DCQL query for the issuers-registry:write scope.
  • POST Token Endpoint: Create and submit a presentation according to the fetched DCQL query.

For further details, please consult our Access Control guide.

Step 2 Register the revocation in the Issuers Registry​

Revocation of a Verifiable Accreditation is done through the Issuers Registry with setAttributeMetadata, by setting the issuerType of the attribute to Revoked:

setAttributeMetadata(subjectDid, attributeId, Revoked, yourDid, yourAttributeId)

The caller must be one of:

  • the attribute's accrediting organisation (its tao),
  • the attribute's Root TAO (its rootTao),
  • a holder of the IssuersRegistry:setAttributeMetadata policy.

Unless the caller holds the policy, it must control the DID it names, and the attribute it names must be a live TAO or RootTAO.

Verifiable Accreditations must contain credentialStatus with type EbsiAccreditationEntry, where validity is determined by the smart contract.

warning

Revocation is a transition on an existing attribute: an attribute cannot be created as Revoked. Once revoked, the attribute cannot be changed again and its body cannot be replaced (setAttributeData reverts).

What happens to the credentials below the revoked accreditation​

  • VCDM 2.0: the whole chain is walked at verification time, so revoking any ancestor makes every credential beneath it fail with Revoked.
  • VCDM 1.1: the verifier only checks the issuer's own accreditation. Revoking a TAO or a Root TAO is not noticed by the credentials of the issuers below it: only revoking the TI's own attribute makes its credentials fail. Revoke each descendant explicitly if needed.
API CALL

Use the following endpoint to modify the attribute metadata using the setAttributeMetadata method:

Ledger Service — eth_sendRawTransaction — Issuers Registry's setAttributeMetadata method