SSL Teams Web Dashboard
This section defines the complete browser-based administration journey for SSL Teams, from first administrator sign-in through certificate-authority setup, configuration, user management, leaf issuance, and lifecycle actions.
The screenshots show a public test deployment with example data. The visible values are included to make the workflow concrete; replace them with values appropriate for your environment.
Guide intent and audience
- Primary audience: administrators and operators running browser-first workflows.
- Primary goal: complete bootstrap, CA setup, user/role management, and first issuance safely.
- Operating model: backend authorization remains authoritative for every protected action.
Use this section for interactive operations in the dashboard. Use the DevOps playbook for CLI-first and automation-oriented operational procedures.
Completion outcomes
By the end of this guide, you should have:
- completed bootstrap authentication and password hardening;
- initialized the application Root and issued the first Intermediate;
- configured role-based access for operators and reviewers;
- issued at least one leaf certificate for explicit DNS/IP identities; and
- validated lifecycle visibility for active, retired, and revoked material.
End-to-end flow
flowchart TD
A[Deploy SSL Teams] --> B[Sign in]
B --> C[Change bootstrap<br/>password]
C --> D[Create application<br/>Root]
D --> E[Store Root backup<br/>offline]
E --> F[Create<br/>Intermediate]
F --> G[Review<br/>dashboard]
G --> H[Manage users<br/>and roles]
H --> I[Review system<br/>configuration]
I --> J[Issue leaf<br/>certificate]
J --> K[Monitor and manage<br/>lifecycle]
Before you begin
- Deploy SSL Teams and confirm the HTTPS service is reachable.
- Keep initial administrator credentials available only to the bootstrap owner.
- Prepare a protected offline location for the application Root private-key backup.
- Define DNS names or IP identities required for the first leaf certificate.
- Define which users need Administrator, Operator, or Viewer access.
Web dashboard workflows
- Bootstrap and CA setup
- Dashboard and monitoring
- User and role management
- System configuration
- Leaf certificate issuance
- Certificate lifecycle actions
Certificate layers
SSL Teams uses separate certificate layers for separate purposes:
- The server TLS certificate protects the HTTPS connection to the SSL Teams service.
- The application Root is the trust anchor for certificates managed by the application.
- The Intermediate is the normal issuing authority for leaf certificates.
- A leaf certificate represents a service, host, or other issued identity.
The server TLS certificate and the application Root are not interchangeable. Configure and trust each layer for its intended purpose.
After completing the guide
Continue with the Deploy With Docker and DevOps Playbook pages for deployment and operating procedures. For application integration, see the Spring Boot 4 HTTPS Demo and Quarkus 3.33 HTTPS Demo.