SSL Teams demos
These standalone Maven applications show how to run an HTTPS application with a leaf certificate issued by SSL Teams. Both examples serve GET /hello on port 8443 and use the DNS SAN localhost.
Before you start
- Deploy SSL Teams and make sure its application CA is ready.
- Install the
sslteamCLI, authenticate it, and confirm that it can reach the service. - Use Java 25, Maven, OpenSSL, and curl.
- Run the demo commands from
sslteam-services/demos/.
The examples do not include certificates, private keys, keystores, or passwords. Generate those artifacts locally and keep them out of source control.
Certificate roles
localhost.p12is the Spring Boot server identity keystore. It contains the private key and certificate chain.fullchain.pemandleaf-key.pemare the PEM server identity files used by the PEM alternatives.root-ca.pemis a public trust anchor for clients. It is not a server certificate, private key, or keystore.
The certificate identity must match the URL. These examples use https://localhost:8443; an IP URL requires a certificate with the matching IP SAN.
Trust safely
Inspect the Root certificate and compare its SHA-256 fingerprint with an independently approved value before installing it:
openssl x509 \
-in /protected/path/root-ca.pem \
-noout -subject -issuer -dates -fingerprint -sha256
For a single request, use an explicit CA file:
curl --cacert /protected/path/root-ca.pem \
https://localhost:8443/hello
You can install the approved Root certificate into the native trust store for local development, then verify the installation:
sslteam ca trust install \
--certificate /protected/path/root-ca.pem \
--confirm-fingerprint <approved-sha256-fingerprint>
sslteam ca trust verify \
--certificate /protected/path/root-ca.pem \
--confirm-fingerprint <approved-sha256-fingerprint>
Remove the Root certificate when the development environment is retired. Do not use curl -k; it disables the trust and hostname checks these demos are intended to verify.