How ctt-gob-es/fire works
Main Components Overview
a. Central Component (Server-side):
• fire-signature (Core component)
• clavefirma-test-services (Cl@veFirma simulator)
• fire-admin-web (Administration application)
b. Distributed Client:
• fire-client (Integration libraries in Java, .NET, and PHP)
Detailed Architecture
A. Central Component:
• [Central Component]
• Core Services (fire-signature)
• Signature Service
• Authentication Service
• Document Management
• Statistics Service
• Administration (fire-admin-web)
• User Management
• Application Management
• Certificate Management
• Log Management
• Test Services (clavefirma-test-services)
• Cl@veFirma Simulator
B. Distributed Clients:
• [Client Libraries]
• Java Client
• .NET Client
• PHP Client
Integration Points
• Connections to external services (Cl@veFirma, FNMT)
• Database connections for persistence
• Integration with document management systems
Security Layer
A security layer showing:
• SSL/TLS communication
• Certificate-based authentication
• User authentication flows
• Authorization mechanisms
Supporting Components
Additional components:
• fire-statistics-common (Statistics handling)
• fire-log-handlers (Logging system)
• fire-upgrade (Signature upgrade services)
• fire-alarms (Monitoring and alerts)
Data Flow
• Client requests → Central Component
• Authentication flows
• Signature processes
• Document management
• Administrative operations
Deployment View
A separate section showing:
• Web container deployment
• Database servers
• Load balancers (if applicable)
• High availability configuration
Notes
Important notes about:
• Required external dependencies
• Configuration requirements
• Security considerations
• Scalability options
Integration with external services
Remember to include version information and any specific deployment requirements noted in the README, such as the need for private libraries for certain connectors (Cl@ve Firma and CloudId).