How sunet/vc works
VC is a Go microservices platform for issuing and verifying digital credentials. A wallet requests issuance through the API Gateway, which handles authorization and consent and delegates signing to the Issuer; the Registry manages credential status lists. For verification, a relying party starts an OIDC flow with the Verifier, which requests a wallet presentation through OpenID4VP and returns the verification outcome. The README documents these principal flows and optional SAML/OIDC identity-provider paths; sampled source confirms service wiring, but not every runtime call in unsampled modules.
Main entry points: handlers_oauth.go Gateway API · openid4vp OpenID4VP · apiv1 Verifier API · grpcserver Issuer gRPC
Components 20
Credential issuance
- Gateway API
internal/apigw/apiv1/handlers_oauth.go - Issuance challenge
internal/apigw/apiv1/handlers_oauth_challenge.go - Issuer API
internal/issuer/apiv1/client.go - Issuer gRPC
internal/issuer/grpcserver
Credential verification
- Verifier HTTP
internal/verifier/httpserver/verification_routes.go - Verifier API
internal/verifier/apiv1 - OpenID4VP
pkg/openid4vp - Mdoc verification
pkg/mdoc/openid4vp_handler.go - SD-JWT verification
pkg/sdjwtvc/openid4vp_handler.go - VC 2.0 verification
pkg/openid4vp/vc20_handler.go - OIDC provider
internal/verifier/apiv1/handler_oauth.go
Platform services
- Gateway HTTP
internal/apigw/httpserver/service.go - Gateway datastore
internal/apigw/db - Registry API
internal/registry/apiv1/handlers_token_status_list.go - Status-list issuer
internal/registry/tokenstatuslistissuer/service.go - Registry database
internal/registry/db
Identity integrations
- Auth providers
internal/apigw/auth_providers
Other components
- Wallet
- Relying party
- External IdP
Connections 20
- Wallet → Gateway HTTP: requests issuance
README.md - Gateway HTTP → Gateway API: routes requests
internal/apigw/httpserver/service.go - Gateway API → Issuer gRPC: delegates signing
README.md - Issuer gRPC → Issuer API: serves issuance
- Gateway API → Registry API: uses status service
README.md - Gateway API → Gateway datastore: looks up documents
README.md - Gateway API → Issuance challenge: handles challenge
- External IdP → Auth providers: authenticates user
README.md - Gateway API → Auth providers: selects provider
- Registry API → Status-list issuer: issues status lists
- Status-list issuer → Registry database: reads and writes
internal/registry/tokenstatuslistissuer/service.go - Relying party → Verifier HTTP: starts OIDC flow
README.md - Verifier HTTP → Verifier API: routes verification
internal/verifier/httpserver/verification_routes.go - Verifier API → OIDC provider: handles OIDC
README.md - OIDC provider → Wallet: requests presentation
README.md - Wallet → OpenID4VP: submits presentation
README.md - Verifier API → OpenID4VP: verifies presentation
- OpenID4VP → Mdoc verification: handles mdoc
- OpenID4VP → SD-JWT verification: handles SD-JWT
- OpenID4VP → VC 2.0 verification: handles VC 2.0