Product Overview
SSL Teams centralizes certificate authority operations while keeping authorization, scope, lifecycle, and audit decisions on the server. It is designed for teams that need short-lived development or private-infrastructure certificates without distributing a CA signing key to every client.
As an HTTPS certificate management platform for development PKI, SSL Teams helps engineering, platform, and security teams standardize internal TLS identity issuance, trust distribution, and lifecycle governance.
This page explains system shape, trust boundaries, and responsibility split. For step-by-step operations, use the Operator Guide or DevOps playbook.
Where SSL Teams fits best
- Teams replacing ad hoc certificate scripts with a controlled service workflow.
- Development and private infrastructure environments that need explicit trust and identity handling.
- Organizations that need auditable certificate lifecycle operations across teams and environments.
Runtime shape
graph TD
C[Dashboard or sslteam CLI] -->|HTTPS| A[app-main Quarkus service]
A --> AR[auth-rest]
A --> CR[cert-rest]
AR --> AS[auth-service]
CR --> CC[cert-core]
AS --> P[(PostgreSQL)]
A --> W[React dashboard]
The deployable app-main runtime serves the dashboard and API from one HTTPS origin. The default HTTPS port is 15080, insecure HTTP fallback is disabled, and operator health checks run through a loopback-only management interface on port 9000. Production does not publish an OpenAPI or Swagger UI endpoint.
Three certificate layers
startup TLS certificate
protects HTTPS between a client and the SSL Teams service
application Root CA
signs the application Intermediate CA
signs development leaf certificates
These layers have different owners and different trust decisions. The startup certificate identifies the service. The application Root CA and application Intermediate CA form the application CA used to issue development identities.
A normal workflow
- A service owner deploys SSL Teams with PostgreSQL, startup TLS state, and protected JWT signing material.
- An operator verifies the service origin and establishes CLI transport trust.
- The operator authenticates and selects a team and environment scope.
- SSL Teams creates or activates the application Root and Intermediate through a protected workflow.
- An authorized caller requests a leaf certificate with explicit DNS or IP SANs.
- The service records the issuance and returns the requested artifact or public material.
- Operators inspect inventory and audit history before planned retirement or security revocation.
Scope and authority
Certificate operations are scoped by a team and environment. The CLI can store preferences for those values, but local configuration never grants permission. The backend checks authentication, authorization, scope, certificate policy, lifecycle state, and optimistic-lock versions for protected operations.
What SSL Teams does and does not do
- SSL Teams does provide server-side authentication, authorization, scoped certificate operations, and audit history.
- SSL Teams does provide dashboard and CLI workflows for Root/Intermediate lifecycle and leaf issuance.
- SSL Teams does not rely on browser route guards or local CLI preferences as security controls; backend checks remain authoritative.
- SSL Teams does not merge transport trust with certificate identity verification; each decision remains explicit.
Public project surfaces
| Surface | Responsibility |
|---|---|
app-main |
Deployable Quarkus runtime, HTTPS, dashboard packaging, health, and OpenAPI generation |
auth-service and auth-rest |
Users, teams, roles, permissions, tokens, passwords, and device authorization |
cert-core and cert-rest |
Certificate identity, CA workflows, issuance, downloads, lifecycle, and audit |
sslteam-api |
Framework-neutral Java request, response, scope, inventory, and audit contracts |
sslteam-client |
Typed Java transport and service client for CLI and integrations |
cli |
The standalone sslteam operator and automation client |
web |
React dashboard and browser API client |
Do not treat the dashboard as the authority
Browser route guards and CLI preferences improve the user experience, but the backend remains authoritative for every protected operation.