How webprofusion/certify works
Main Components
• UI/Client Layer:
– Projects: Certify.UI, Certify.UI.Desktop, Certify.UI.Shared.
– Function: Provides the graphical interface (and some user-interactive dialogs) for certificate management.
• Business Logic/Core Layer:
– Projects: Certify.Core, Certify.Models, Certify.Shared.
– Function: Contains business logic such as certificate request management, challenge processing, renewal logic, configuration management, and core data models.
• API/Service Layer:
– Projects: Certify.Server (with its various subprojects like Certify.Server.Core, Certify.Server.Hub.Api, and Certify.Server.HubService) and Certify.Service.
– Function: Exposes HTTP endpoints (REST APIs) and background service interfaces (SignalR hubs, OWIN services) that handle client requests, orchestrate certificate requests, and perform backend tasks.
• Plugin/Provider Layer:
– Projects: Certify.Providers and Certify.Shared.Extensions.
– Function: Implements integration with external certificate authorities (via ACME) and DNS challenge providers, as well as providing deployment and other extension points.
• CLI Tool:
– Project: Certify.CLI.
– Function: Offers command-line functionality to perform tasks (certificate activation, import/export, deployment) that complement the UI.
• Supporting & Testing Components:
– Projects: Certify.Tests (unit and integration tests) and associated scripts (in the scripts folder) for builds, deployment automation, and packaging (e.g., Chocolatey scripts).
Relationships and Interactions
• The UI layer communicates with the API/Service layer (via HTTP, SignalR, and possibly other IPC mechanisms) to trigger certificate requests, renewals, and status updates.
• The API/Service layer calls into the core business logic (Certify.Core and Certify.Models) to process certificate requests and facilitate deployments.
• The Plugin/Provider layer interfaces with external services – for example, ACME certificate authorities (Let's Encrypt, BuyPass, ZeroSSL, etc.) and different DNS APIs – to conduct validation challenges.
• The CLI tool provides an alternative entry point that interacts with the API and business logic; in deployment scenarios, it may be used to script or automate certificate management.
• Background services (such as the Windows background service in Certify.Server.Core and Certify.Server.HubService) automatically handle renewals and updates, ensuring the certificates remain valid.
Architectural Patterns and Design Principles
• Layered Architecture: Separation between presentation (UI), business logic (Core/Models), and API/service layers.
• Plugin Architecture: Clearly separated providers and shared extensions that enable integration with multiple ACME and DNS providers.
• Service-Oriented/RESTful API Interfaces: The server components expose REST endpoints and use SignalR hubs for real-time updates.
• Modularity: The project is broken into multiple small, purpose-specific projects (CLI, Server, UI, Providers, etc.) to enhance maintainability and extensibility.
• Automated Testing/CI: Presence of GitHub workflows (YAML under .github/workflows) and extensive test projects show a commitment to continuous integration and testing.
Relevant Technologies and Frameworks
• .NET Core/Framework (C#) is the primary language and platform.
• SignalR for real-time communication between the UI and service.
• Docker (as seen in .dockerignore and test Dockerfiles) for containerized testing.
• Windows Data Protection API for credential storage.
• Various configuration and deployment tools (including PowerShell scripts and Chocolatey packaging scripts).