- Home
- Credentialing Software
- DCC Issuer Coordinator
On the recordRead 11 Oct 202624 facts
DCC Issuer Coordinator
United States
On the record
- API
- The service implements VC-API endpoints for issuing credentials and updating credential status, plus an endpoint for returning a status list.github.com · read 4 Oct 2026
- Architecture
- It is an Express app that coordinates calls to separate signing and status services running together in Docker Compose.github.com · read 11 Oct 2026
- Audience
- The README presents the issuer for organizations such as schools that integrate credential issuance into their own systems and student portals.github.com · read 11 Oct 2026
- Credential signing
- The README says the issuer supports the did:key and did:web DID formats for signing keys.github.com · read 4 Oct 2026
- Credential status
- Its optional revocation and suspension mechanism implements Bitstring Status List and stores status lists through database or Git services.github.com · read 11 Oct 2026
- Deployment
- The quick start runs prebuilt Docker Hub images through Docker Compose and the README says setup takes less than five minutes.github.com · read 11 Oct 2026
- Endpoint security
- Tenant endpoints can require a Bearer token, and the README suggests IP filtering; setting a tenant token to UNPROTECTED leaves its endpoint unprotected.github.com · read 11 Oct 2026
- Integrations
- The README describes using the issuer from a larger system that prepares a credential and posts it to the issuer, and mentions importing credentials into the Learner Credential Wallet.github.com · read 11 Oct 2026
- Intended users
- The README describes using the issuer within a larger system, such as a school's credential issuance flow, with an API client sending credential data to be signed.github.com · read 4 Oct 2026
- Issuing API
- It implements the VC-API POST endpoints /credentials/issue and /credentials/status.github.com · read 11 Oct 2026
- Key support
- The issuer supports did:key and did:web key formats, and the README recommends did:web for many production deployments because keys can be rotated without updating credentials signed with old keys.github.com · read 11 Oct 2026
- License
- The repository identifies its license as MIT License, copyright 2023 Digital Credentials Consortium.github.com · read 11 Oct 2026
- Multiple issuers
- Tenants allow different signing keys and DIDs to be used for different credentialing purposes.github.com · read 11 Oct 2026
- Production guidance
- The README warns that the shared default signing key is only for testing and evaluation, and says issuers must generate and keep their own signing key private for real credentials.github.com · read 11 Oct 2026
- Purpose
- The app issues signed Verifiable Credentials and allows them to be revoked.github.com · read 11 Oct 2026
- Revocation and suspension
- Optional status management implements Bitstring Status List and can store status lists using database or Git services.github.com · read 4 Oct 2026
- Security guidance
- The README warns that the shared test signing key is unsafe for real credentials and recommends configuring a private key and suggests IP filtering for issuer endpoints.github.com · read 4 Oct 2026
- Setup time
- The project says its four-step quick start should take less than five minutes.github.com · read 4 Oct 2026
