Skip to content

docs: update revocation documentation #1009

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ronjaquensel merged 1 commit into from
Jun 10, 2026
+8 −5
Merged

docs: update revocation documentation #1009

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions docs/developer/architecture/issuer/credential-revocation/credential-revocation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,15 +53,18 @@ credential:
Requests to revoke a holder credential are sent via the IssuerService's REST API:

```http request
POST /v1beta/credentials/{credentialId}/revoke
POST /v1beta/participants/{participantContextId}/credentials/{credentialResourceId}/revoke
```

This request is processed by
the [IssuerCredentialsAdminApiController](../../../../../extensions/api/issuer-admin-api/credentials-api/src/main/java/org/eclipse/edc/issuerservice/api/admin/credentials/v1/unstable/IssuerCredentialsAdminApiController.java)
and delegated to the `CredentialServiceImpl`.

The `credentialId` is the only information that is required to perform the necessary actions. The
`CredentialServiceImpl` performs the following steps:
Next to the `participantContextId`, the `credentialResourceId` is the only information that is required to perform the
necessary actions. Note, that this is the ID of the `VerifiableCredentialResource` that represents the holder
credential, and not the ID of the credential itself.

The `CredentialServiceImpl` performs the following steps:

#### 1. obtain holder credential

Expand Down Expand Up @@ -177,7 +180,7 @@ IssuerService.
Execute the following REST request against the IssuerService's Admin API:

```http request
GET /v1beta/credentials/{credentialId}/status
GET /v1beta/participants/{participantContextId}/credentials/{credentialResourceId}/status
```

the response will be `HTTP 200` if the status information has been obtained. An empty response body indicates that the
Expand Down
2 changes: 1 addition & 1 deletion ...ns/store/sql/identity-hub-credentials-store-sql/src/main/resources/credentials-schema.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
-- only intended for and tested with Postgres!
CREATE TABLE IF NOT EXISTS credential_resource
(
id VARCHAR PRIMARY KEY NOT NULL, -- ID of the VC, duplicated here for indexing purposes
id VARCHAR PRIMARY KEY NOT NULL,
create_timestamp BIGINT NOT NULL, -- POSIX timestamp of the creation of the VC
issuer_id VARCHAR NOT NULL,
holder_id VARCHAR NOT NULL,
Expand Down
Loading