Certificates pages
A screen-by-screen tour of the certificate list (filters, CSV export, bulk renew), the four-step issue wizard, and the detail page with its action buttons, risk panel, timeline, dependency graph, and Distributions tab. For the concepts behind the screens, follow the cross-links — this page is about what you see and click.
Open it from the sidebar: Certificates → Certificates. The page is project-scoped.
The certificate list
Header controls
- Search box — free-text search across certificates.
- Status filter — Active · Pending · Expired · Revoked · Renewal Failed.
- Issuer filter — ACME · MSCA · Imported · CA Connector.
- Expires in filter — 7 / 30 / 60 / 90 days.
- A Clear button appears when any filter or search is active, and a blue N filters active tag next to the title keeps count.
- Export CSV — opens the CSV export endpoint in a new tab, honouring the current search term. The file has the serial in decimal (Serial Number) and, in the last column, in hexadecimal (Serial Number (hex)).
- Refresh — immediate refetch.
- Import — opens the import page to upload an externally-issued certificate (bring-your-own) as pasted PEM, certificate + key files (PEM, DER, PKCS#7) or a PFX / P12 file. Shown only to project admins (the route needs the Admin role). Disabled at the license/plan limit.
- Issue Certificate — opens the issue wizard. Shown to operators and admins (a viewer cannot issue). Disabled with a Certificate limit reached tooltip when your license/plan limit is hit.
Filters can also arrive pre-set via URL parameters (?status=, ?issuer_type=, ?expires_in_days=, ?expiring_within=) — links from the dashboard use this. expires_in_days is a calendar window; expiring_within is the dashboard's rule, which caps the window at a third of each certificate's lifetime.
Columns
| Column | Content |
|---|---|
| Name | Certificate name. Sortable. |
| Primary Domain | First domain on the certificate. Sortable. |
| Status | Coloured status tag (active, pending, issuing, awaiting validation, renewal failed, expired, revoked, …). A red Issuance failed tag is appended when the last attempt to issue the certificate failed and nothing is retrying it — a failed first issuance stays pending, because nothing was issued and the next move is to try again, so this tag is what tells it apart from a certificate created moments ago. A neutral Dist. Pending tag is appended when a delivery is still outstanding. |
| Issuer | ACME (blue), MSCA (purple), Imported (gold) or the connector vendor's name — e.g. GlobalSign Atlas — (cyan) tag plus the issuer CN. |
| Key Type | e.g. ECDSA-P256, RSA-2048. |
| Validation | Imported (bring-your-own, no CA validation), Manual (manual DNS validation), HTTP (HTTP-01), or Auto (automatic DNS). |
| Auto Renew | On / Off tag. |
| Expires | Days-left tag — red at ≤ 7 days, orange at ≤ 30, hover for the exact timestamp. Sortable. |
| Actions | Renew (active, renewal-pending, renewal-failed and expired certificates, with confirmation — hidden for imported certs, which cannot renew, and for manual-DNS certs; when renewal approval applies, it files an approval request and opens My Requests instead of renewing) and Delete (with confirmation; blocked with an explanation if other resources depend on it). |
Clicking a row opens the detail page.
Bulk renew
Each row you may renew has a checkbox (imported certificates and certificates you only view have none; a viewer sees no checkbox column). Selecting rows reveals a bulk-action bar with the selection count, a Renew Selected button, and Clear:
- Select the certificates and click Renew Selected.
- Confirm in the dialog — a bulk action job fans out one renewal per certificate.
- A progress bar tracks
succeeded + failed / totalwhile it runs. - On completion you get a success toast, or — if some renewals failed — a Bulk Action Results modal listing each failed certificate with its error (long lists may be truncated).
Mechanics, idempotency, and limits: Bulk renew.
The issue wizard
Certificates → Issue Certificate opens a four-step wizard: Certificate Source → Zone & Domains → Options → Confirm (step 2 is titled just Domains for manual-DNS, HTTP and MSCA flows, which use no zone; for a CA connector it is Zone & Domain). When a certificate policy is enabled, each step shows grey Policy hint chips (allowed issuers, SAN patterns, key types, …) and validates your input live.
Step 1 — Certificate Source
- Certificate Name (required) — friendly name used in dashboards, logs, and distribution references. If a policy naming pattern exists and the name doesn't match, an inline warning shows the expected regex.
- Description / Owner — optional metadata; owner defaults to you.
- Issuer Type — ACME, Microsoft CA or CA Connector radio. Options disallowed by policy are greyed out.
For ACME:
- ACME Account (required) — searchable select showing name, CA provider, and environment. Accounts excluded by policy are disabled. See ACME accounts.
- Organization — appears once an account is selected. Required for OV/EV accounts (organization details go into the certificate Subject); optional for DV, with a warning that most public CAs strip organization fields from DV certificates. For EV accounts the wizard flags missing EV fields (business category, jurisdiction, registration number) on the selected organization before you can sensibly proceed.
- Validation Method — DNS — Automatic (provider API), DNS — Manual (you create TXT records), or HTTP — Automatic (no DNS access needed). See Manual DNS challenge and HTTP validation.
For Microsoft CA:
- MSCA Connection (required) — active connections only (AD CS).
- Certificate Template (required) — templates synced from the connection. Warnings appear if the connection has no synced templates or the template cache is older than 30 days.
For CA Connector (CA connectors):
- CA Connection (required) — active connections in the project; the vendor's name is shown beside each.
- Product — the connection's product catalogue, pre-set to its default. A
*.domain must use a wildcard product and vice versa; when only one product fits it is picked for you.
Step 2 — Zone & Domains
- Domains — one per line, or separated by commas, semicolons or spaces (a pasted list works as is); the first domain is primary;
*.domain.comwildcards are supported. Policy SAN rules are checked live: each denied or not-allowed domain is listed under the field, and exceeding the max SAN count is flagged. - Zones (ACME with automatic or manual DNS) — below the names, the names are grouped by zone: each name starts in the zone with the longest domain it is under (Zones). For automatic DNS every group shows the zone's DNS credential and provider and a zone selector that moves the whole group; clicking a name (or focusing it and pressing Enter) moves just that name or removes it — a name and its wildcard always move together, since they are one DNS challenge. A name no zone covers, a zone without a DNS credential, a name outside the zone chosen for it, or a name listed twice is shown in red and stops Next. Warnings say when one zone's credential makes the whole order run one name at a time (RFC 2136) or in one job (Cloudflare, DigitalOcean, OVH, Plesk), when a name is already covered by a wildcard of the same certificate (Let's Encrypt refuses that order), and when there are more names than Let's Encrypt / Google Trust Services accept (100). Add www. to apex names adds
www.<name>for each name that is one of its zone's domains, unless*.<name>is already on the certificate. Zones you picked are dropped when you change the validation method. For manual DNS the groups only show where each record will go — no zone is needed, and a name can only be removed there. - Zone (CA connector only) — the zone the vendor's validation record is written into; only zones with a DNS credential are listed. Required, except for a vendor that validates domains on its account (GlobalSign Atlas): there it is optional, and without it a domain the vendor has not validated yet fails with
DOMAIN_NOT_VALIDATEDbefore anything is ordered. A vendor that issues single-domain certificates (GlobalSign Atlas) accepts exactly one name. - For manual DNS an info box explains that the required TXT records will be shown on the certificate detail page after submitting; for HTTP validation the info box shows how to route the ACME challenge path to CertAutoPilot and its prerequisites.
Step 3 — Options
- Key Type — ECDSA P-256 (recommended), ECDSA P-384, RSA 2048/3072/4096. Default comes from Settings → General (certificate defaults); policy-disallowed types are greyed out. For a CA connector the list is the vendor's supported set and the default is the vendor's (GlobalSign Atlas: RSA 2048 / 3072 / 4096, default RSA 2048).
- Auto Renew — on by default. Forced off (and locked) for manual-DNS certificates; forced on (and locked) when policy requires auto-renew.
- Renewal Mode (ACME with automatic DNS only) — Custom Threshold or ARI (CA-Suggested). MSCA and CA connectors always use Custom (an info box says so). With ARI the threshold below becomes a fallback.
- Renewal Threshold (days) — 1–90, default from general settings.
- Key Rotation Policy — Reuse key or Rotate key on each renewal.
Renewal semantics: Renewal.
Step 4 — Confirm
A summary of everything you chose. Click Issue Certificate:
- Preflight warnings — if the backend flags issues, a modal lists them and asks you to Proceed Anyway or cancel.
- Approval required — if issuance is gated for your role, an approval request is created instead and you're redirected to Approvals.
- Otherwise you land on the certificate detail page while the issuance job runs. Follow it live from the job detail.
Policy violations that slip past the live checks are rejected server-side with structured errors (Policy engine). The full issuance flow: Issuance.
The detail page
Action buttons
The header row shows Back plus context-dependent actions:
| Button | Shown when | Notes |
|---|---|---|
| Download | the certificate holds a current version (whatever its status — an expired or renewal-failed certificate included), or it is active / revoked | Dropdown of formats: Full Bundle (.pem), Certificate (.crt), Full Chain, Chain, Private Key, PFX, DER, JKS, or Download All Files (zip). PFX/JKS first ask for an optional password (and alias for JKS), then show a one-time password modal — the password is not stored. A JKS password takes Latin-1 characters only (what Java can open); the dialog stays open when a download is refused. May require approval (Download). |
| Manual Renew | status is active, renewal_pending, renewal_failed or expired, and validation is not manual DNS | Asks for confirmation first (the same as the list's Renew). The licence certificate limit never blocks renewals — existing certificates are grandfathered (License). For a CA-connector certificate the confirm dialog says whether the renewal reissues the existing vendor order (no purchase) or requests a new certificate from the vendor (one unit of your quota or credit). |
| Re-issue | ACME (automatic DNS, HTTP or manual DNS) and AD CS certs in active/renewal_failed/expired; manual-DNS certs in awaiting_validation; stuck pending certs with an error or nothing advancing them (for AD CS: a first issuance the CA refused); AD CS certs in msca_pending_expired; CA-connector certs in pending (with an error or nothing advancing it), renewal_failed or expired — active only when the vendor can reissue its order for free | Requests a fresh issuance with a new key, after a confirmation; for a valid certificate it says the current certificate stays valid and is not revoked (Reissue). Hidden while a revocation of the certificate is queued or running (a line on the page says so; Renew is hidden too), refused while a renewal is running; an operator who needs approval gets the same refusals at request time, so no request is filed that could never run. |
| Cancel re-issue | on the DNS Challenges card while a manual-DNS re-issue of a valid certificate waits for its TXT records | Abandons the pending records; the certificate returns to its previous status with its current key (Reissue). |
| Revoke | status is active, expired, renewal_pending or renewal_failed, ACME only (no CA connector revokes from CertAutoPilot yet) | Opens a modal with an irreversibility warning; you must type REVOKE to enable the button (Revoke). |
| Re-import | issuer type is imported | Opens the import page in re-import mode to upload a fresh certificate (a new version; the old one is kept in history). Admin role. |
The ⓘ button next to the actions explains what Renew and Re-issue do for the certificate's issuer (ACME or AD CS: the key, the validation and what happens to the current certificate; a CA connector also lists Rekey and the vendor quota).
For imported (bring-your-own) certificates, Manual Renew / Re-issue / Revoke are hidden — there is no CA behind them; Download and Distribute stay available, and the refresh path is Re-import.
Renew, Reissue, Revoke, and Download all detour to the approval workflow when gated — you're redirected to Approvals.
Status banners
Depending on state, alert banners appear above the overview: awaiting approval (links to My Requests), rejected (with the reviewer's reason), DNS cleanup failed (leftover _acme-challenge TXT records), MSCA pending CA approval (polled automatically), MSCA pending request expired (with a Retry Issuance button), last re-issue failed (the current certificate is unchanged; with a Re-issue button), the CA refused the renewal (AD CS: automatic renewal stopped until Renew), the CA-connector banners — keyed by the code at the start of Last error: certificate quota used up, domain not validated, domain validation failed, the connection has no mTLS client certificate, the mTLS client certificate is not usable, vendor unreachable (nothing ordered — check this server's firewall, DNS and proxy, then re-issue), order request unanswered, validation record could not be written, order deadline exceeded, certificate for another name or key (refused, never stored), plus a generic banner for any other vendor code; they appear for a failed first issuance and for a connector renewal in renewal_pending / renewal_failed — and expiry warnings — red at ≤ 7 days with a Renew Now button (or an Auto-renew enabled tag), yellow at 8–30 days.
Overview card
A bordered descriptions table: status, key type, primary domain, all domains (collapsed past 5), validation method (credential name + provider for automatic DNS, or a Manual DNS / HTTP tag), issued/expires timestamps with a days-left tag, SHA-256 fingerprint and serial number (copyable; the serial is shown in hexadecimal, as openssl, browsers and the Chain tab show it, with the decimal form in its tooltip), owner, description, issuer CN, and — depending on issuer type — the ACME account (provider, staging tag) or the MSCA connection, template, and CA request ID, or the CA connection, vendor, product and vendor order id. When available it also shows OCSP status (with last-check time and revocation source), a distribution tag — Scheduled with the time the window opens when the wait is a schedule window, otherwise Pending with the time the wait began — next renewal time, and the last error. An Issuance failed tag sits next to the status when the last issuance attempt failed with nothing retrying it; the reason is in Last Error and Re-issue starts a fresh attempt. While a re-issue of a valid certificate runs, the progress card and the DNS Challenges card say that the current certificate stays valid and downloadable until the new one is issued. The pencil icon (operators and admins) edits owner and description.
Risk Assessment
A card under the overview. A healthy certificate shows a green Healthy state with an expandable Checks Performed list; anything else shows a circular score (0–100), a level tag (LOW/MEDIUM/HIGH/CRITICAL), the weighted Risk Factors, and informational Attention Signals. Scoring model: Risk scoring.
Vendor order (CA connectors)
For a CA-connector certificate that is issuing or renewal_in_progress, a Vendor order card shows the order id, the validation record the vendor asked for (name, type, value — copyable) with the DNS provider and time it was written, whether it has been seen on the configured resolvers, how many times the vendor has been asked and its last answer code, and the order deadline. While a vendor that validates domains on its account (GlobalSign Atlas) is still validating them, no order id is shown yet — the job log of ca_poll_order names each domain and its record. Once the order closes the card shows the outcome; a DCV cleanup failed warning names the record to delete by hand.
Manual DNS challenges
For manual-DNS certificates in awaiting_validation, a DNS Challenges card lists the TXT records to create (copyable name and value, per-record expiry, plus the ACME order deadline). Use Check Propagation to query three public resolvers per record — each row shows Propagated, Partial, Mismatch, or Not found. Tick I have created the TXT records, then Validate DNS Records to enqueue validation. See Manual DNS challenge.
Renewal Policy card
Auto-renew switch, renewal mode (ARI or custom threshold), threshold days, the ARI window and last ARI check (ARI mode), key rotation policy, rotate-every-N counter, and renewal attempts used vs max.
Edit (operator, not on a certificate awaiting approval, rejected or revoked) changes the renewal settings after issuance: auto-renew, renewal mode, threshold, key rotation and rotate-every-N. The same rules as the issue wizard apply: ARI only for ACME certificates validated over DNS-01 or HTTP-01, no auto-renew for a manual-DNS certificate, and a CA-connector threshold must leave room for the vendor order deadline. Changes apply from the next renewal; a threshold larger than the remaining lifetime makes the certificate due at the next scheduler run (refused with a hint when the approval policy gates your renewals). Imported certificates have no renewal settings — re-import them instead.
Tabs
The bottom card has these tabs (a Discovery tab lists where scans have seen the certificate):
- Jobs — recent jobs for this certificate (type, status, attempts, triggered by, duration, error) with a Retry button on failed/dead rows; click a row for the full job detail.
- Certificates — artifact version history: a Version column (
v1,v2, …), which PEM is current, serial, expiry, created date, and a per-row Download button to export any past version (cert, chain, key, or a zip). The version number is what the rollback version picker refers to. See Download a certificate → version history. - Keys — private-key history with type and fingerprint; relevant with the rotate key policy.
- Distributions — see below.
- Dependency Graph — see below.
- Timeline — the certificate event stream: coloured tags per event type (requested, issued, renewed, distributed, failed, …) with message, timestamp, and job/host/error-code chips; Load More pages backwards. Event catalogue: Timeline events.
- Access — shown to an admin of the certificate: which members whose project role is limited to granted resources may reach it, and with which role. Add a member, change the role or remove it, then Save access (Resource grants).
Distributions tab
Links this certificate to distribution modules and runs deliveries. A compact summary strip above the tabs also counts linked modules by last result (success / unverified / partial / failed / pending).
- Link Module — pick an enabled module config (Distribution primitives), toggle Enabled (a disabled link is skipped by automatic runs — renewal, sweeps, schedule wakes — while a manual Distribute now still runs it, so you can test one before switching it on), and — for any rollback-capable module — optionally Auto Rollback on Failure (Rollback).
- Each linked row shows the module type tag and name, a schedule badge, the last status, last-distributed time, and the last error.
Status tags: Not executed, Running, success, unverified (gold — every target deployed but the post-deploy validation could not confirm it yet; an automatic re-check follows five minutes later, see validation), partial (with an ok/skipped/failed breakdown), failed, and v{n} rolled back (gold — the targets carry an older version; the state is sticky until the next renewal rolls forward, or you run the distribution again). Alongside the status sits a fingerprint comparison tag: v{n} current (deployed artifact matches this certificate) or outdated (a newer artifact hasn't been pushed yet). outdated is suppressed while a distribution is rolled back — carrying an older version is the intended state there, and the v{n} rolled back tag already says so. While a large distribution fans out, a n/m batches progress indicator appears with a retrying tag when failed targets are being retried automatically (Fan-out).
Per-row actions:
- Auto-distribute switch — enables/disables automatic distribution after renewals (manual Run still works when off).
- Schedule (clock icon) — opens the schedule editor for maintenance-window distribution.
- Run — executes distribution to all targets (confirmation dialog). The page polls faster for the next 30 seconds so results appear quickly.
- Dry Run — no changes made; a modal shows per-target reachability, the planned actions (upload/update/exec) per target, warnings, and — for IIS — the discovered HTTPS bindings and app pools. The summary reads All checks passed or Some checks failed; a target that answered but whose check refused the plan is tagged Check failed (one that could not be reached, Unreachable). Each target shows how long it took, with each remote step's time on hover. Plans are paged at 20 rows and only the first 10 targets open expanded — the rest expand on click. When the dry run's 100-second budget ran out before some targets were reached, a warning at the top says how many were not checked; if the browser stops waiting, the page shows Dry run did not answer in time.
- Rollback — shown when the module is rollback-capable and at least one previous retained version is eligible; opens a version picker (radio list of retained versions, newest first, ineligible rows disabled with the reason) (Rollback).
- Job — jumps to the last (or currently running) distribution job.
- Unlink — removes the link; future distributions skip this module.
Expanding a row reveals the per-target results table (filterable All / Failed / Changed / Skipped): target name and type, status (including retry pending), post-deploy action and exit code, duration, error with a code-specific hint, post-distribution validation results (expand a target for per-endpoint detail), warnings, raw execution detail, and a link to the target's job.
Dependency Graph tab
An interactive Graph / Table view of everything this certificate depends on and delivers to: ACME account or MSCA connection, zone and DNS credential, organization, distributions, module configs, targets and target groups, module credentials, path sets and action sets — with broken references highlighted as Missing Ref nodes and per-target distribution status colouring. Concept and use-cases: Dependencies.
See also
Video tutorials
Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →