Manage wizard
Adopt a discovered certificate into full CertAutoPilot management. The wizard creates a new certificate — from an ACME CA or from Microsoft AD CS — for the same names, links it to the discovered record, and starts issuing it straight away — after which renewal, revocation and distribution work as for any other managed certificate.
What managed vs shadow means
- Shadow / unmanaged (before): The cert exists in
discovered_certificates. CertAutoPilot knows about it but doesn't renew, revoke, or distribute it. - Managed (after): A new record is created in
certificateswith the chosen ACME account or AD CS connection and issued immediately. The discovered record is linked to it and shows Managed in the inventory.
The wizard does not take over the existing certificate or its private key — it issues a replacement. To bring the existing certificate under management as it is, use Import with private key on the certificate's detail page (see Discovery inventory → Import) or certificate import.
Prerequisites
- Operator role on the project.
- An ACME account that can issue for the same identifiers, or an active Microsoft AD CS connection with synced templates.
- For ACME automatic DNS validation, a registered zone covering the names. Manual DNS, HTTP-01 and AD CS need no zone.
Run the wizard
- Discovery → Inventory → click the cert → Manage with CertAutoPilot (or Manage on the inventory row).
- Review — the subject, issuer, expiry, key, the endpoints where the cert was seen, and Where it can go: the places it was seen that can become distribution targets, with the targets that already point there (shown only — nothing is linked).
- Configure — certificate name (suggested from the subject), description, owner and where to issue from: an ACME CA (the ACME account, an organization for OV/EV accounts, and the validation method — automatic DNS, manual DNS, or HTTP) or Microsoft AD CS (the connection and the certificate template). AD CS is offered when the project has an active connection and the certificate policy allows it. When the policy allows no ACME and AD CS cannot be used either, the step says so and does not continue — import the certificate with its key from the certificate page instead.
- Zone & Domains (Domains for manual DNS / HTTP / AD CS) — the domain list, pre-filled from the names the scan found, and for automatic DNS the zone that validates each name: the names are grouped by the zone with the longest domain each one is under, and a group or a single name can be moved to another zone, so the names may span several zones (Names in several zones). If you can't reissue with exactly these identifiers (e.g. an IP SAN your CA doesn't allow), adjust the list or fix the source of truth first.
- Options — key type (defaults to matching the discovered key), auto-renew, renewal threshold, key rotation policy. The renewal defaults come from General settings; manual-DNS certificates cannot auto-renew.
- Confirm — review and submit. Issuance starts immediately and you land on the new certificate's page. If issuance requires approval, a request is created and you are taken to My Requests instead. For AD CS, warnings about the connection (templates not synced recently, credentials changed since the last successful sign-in) are shown first and you choose whether to proceed — the same check as a new AD CS certificate.
The project's certificate policy applies as for any new issuance: disallowed key types and issuers are greyed out, and names are checked against the SAN rules as you type.
What happens after adoption
- The discovered record is linked to the new managed certificate and shows Managed in the inventory.
- The renewal scheduler includes the new certificate in its regular sweep.
- The old certificate keeps serving until you deploy the new one. Attach distributions to the managed certificate to roll it out to the endpoints the scan found.
Removing management
There is no "un-manage" button. If you added a cert by mistake, delete the managed record (Certificates → … → Delete). The discovered record remains and reverts to Not managed.
Troubleshooting
No zone to pick
None of your registered zones covers the names. Register the zone first, or choose manual DNS or HTTP validation.
Issuance failed
The new certificate is an ordinary ACME or AD CS issuance — a public CA refusing an internal-only name, a CA rate limit, or a validation failure shows up on the certificate's page and job log. See Issue a certificate.
See also
Video tutorial
Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →