Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform
FAQShort answer
A wildcard certificate is a certificate that carries a name in the form *.example.com in its SAN list and covers all the subdomains of a domain at a single level: www.example.com and api.example.com are in scope; example.com itself and two-level names such as a.b.example.com are out of scope. In TR7, a wildcard certificate is added to the SSL/TLS Certificates screen like other certificates and is selected in the Certificate field of the vService; when it is obtained automatically with ACME, it can be obtained only with Challenge Type = DNS-01.
| Where | Field / label | What for |
|---|---|---|
| Certificates & PKI → SSL/TLS Certificates → Add → ACME.SH | Challenge Type = DNS-01, DNS Provider | Obtaining the wildcard certificate with ACME; if a name that starts with *. is entered while HTTP-01 is selected, the form gives the Wildcard domains require the DNS-01 challenge error |
| SSL/TLS Certificates → Add → Manual or PFX | Certificate content or PFX file | Uploading a wildcard certificate obtained from another CA |
| SSL/TLS Certificates → CSR (External CA) | Subject Alternative Names | Writing the *.example.com name into the CSR and having it signed by an external CA |
| HTTP vService and L7 TCP vService | Certificate | Presenting the wildcard certificate; if a certificate whose name matches exactly is also selected, that certificate is presented first |
*.example.com also covers the main domain." It does not; for example.com, the name is added to the SAN list separately.* stands in for only the single leftmost label; a.b.example.com is out of scope (RFC 9525).How it is done in the documentation

Reach us for your questions and support requests.
This document is digitally signed and timestamped.