How digitalcredentials/signing-service works
Main System Components
a) HTTP Server Layer
• Express.js server handling four main endpoints:
• POST /instance/:instanceId/credentials/sign
• GET /did-key-generator
• POST /did-web-generator
• GET /healthz
b) Tenant Management System
• Multi-tenant architecture supporting multiple signing keys
• Tenant configuration management
• Seed storage and management
c) Signing System
• Credential signing logic
• DID key generation and management
• Support for both did:key and did:web methods
d) Middleware Layer
• Access logging
• Error handling
• Error logging
• Invalid path handling
External Integrations
Connections to:
• DID Registries (for key verification)
• Health check notification systems (SMTP/Slack)
• Docker health check system
[HTTP Layer] → [Middleware Layer] → [Tenant Management] → [Signing System]
Component Relationships
Key flows:
a) Credential Signing Flow:
Client → HTTP Endpoint → Tenant Validation → Signing Process → Signed Credential
b) DID Generation Flow:
Client → Generator Endpoint → Key Generation → DID Document Creation → Response
c) Health Check Flow:
Docker → Health Check → Service Test → Notification System
Important Details
a) Configuration Elements:
• Environment variables
• Tenant configurations
• Logging settings
b) Security Boundaries:
• DID verification zones
• Tenant isolation
• Key management boundaries
c) Monitoring Points:
• Health check paths
• Logging points
• Error handling flows
Technical Specifications
Technical details:
• Node.js/Express.js as the primary runtime
• Docker containerization
• Support for both did:key and did:web methods
• Logging levels and destinations
• Health check mechanisms
Integration Points
Integration points for:
• DCC issuer-coordinator
• DCC workflow-coordinator
• External DID registries
• Monitoring systems
Remember to emphasize the service's role within the larger DCC ecosystem while showing its capability to function as a standalone service.