Every deployment TigerTrust performs captures a snapshot of what was previously live on the target before the new certificate is pushed. If the new certificate causes a service disruption — mismatched chain, wrong SAN, revoked upstream CA — you can restore the prior state in seconds without hunting down old certificate files.

​
What it is

Before replacing a certificate on a target, TigerTrust automatically saves the outgoing certificate, its chain, and the deployment configuration. That snapshot is attached to the deployment job record. If something goes wrong, clicking Rollback creates a new deployment job that pushes the saved snapshot back to the target. The original forward job remains in the history, so the full incident sequence is auditable.

​
When to use it

  • A renewed certificate is pushed to a load balancer and health checks immediately fail — roll back in one click while you diagnose the renewal issue.
  • A script-based deployment completes but the service reports trust errors because the intermediate chain changed — restore the previous bundle within the deployment window.
  • A blue/green cutover goes wrong and you need to revert a batch of targets before a postmortem.
  • An automated renewal pushed a certificate signed by the wrong CA profile — roll back to buy time for a corrected re-issuance.

​
Set it up

1

Find the deployment job

Go to Deployments > Jobs and locate the job that needs reverting. Use the status filter to narrow to recent failed or completed jobs.
2

Open the job detail

Click the job row to expand its detail panel. You’ll see the target, the certificate that was deployed, and a Rollback button if a snapshot is available.
3

Confirm rollback

Click Rollback and confirm in the dialog. TigerTrust queues a new rollback job immediately.
4

Watch the rollback job

The rollback job appears at the top of the Jobs list. Its log streams in real time. When it reaches Completed, verify service health on the target.

​
What you’ll see

After rollback, Deployments > Jobs shows two entries for the target: the original forward job and the new rollback job. Both entries carry timestamps and outcome status so auditors can reconstruct the full timeline. The target’s Current certificate panel reflects the restored certificate.
Rollback succeeds technically even if the previous certificate has since been revoked. Always verify service health after rollback — a revoked certificate will be rejected by clients that check CRL or OCSP status.

Certificate Deployment

The full deployment model: targets, subscriptions, and batches.

Custom Deployment Scripts

Scripts run as part of the deployment job that the snapshot covers.