Update an Expired AIQ Certificate
Update an Expired AIQ Certificate
Use this procedure when an AIQ certificate has expired or is about to expire. Certificate changes should be planned because they can affect browser access, integrations, load balancers, test nodes, and API clients.
Preparation checklist
- Confirm which certificate expired: AIQ application, load balancer, repository, database, or integration certificate.
- Collect the new certificate, private key, intermediate chain, hostname, expiration date, and owner.
- Back up the existing certificate files and configuration before replacing them.
- Schedule a maintenance window if AIQ services, proxy services, or load balancer rules must restart.
- Notify users and integration owners when the certificate change affects external access.
Validation workflow
- Install the renewed certificate and full chain in the approved location.
- Restart only the services required for the certificate to take effect.
- Validate browser access, API access, test-node connectivity, and any load-balanced URL.
- Check logs for TLS, hostname, trust-chain, or expired-certificate errors.
- Record the new expiration date and renewal owner.
Last updated: October 9, 2026