Note: Please ensure to take valid snapshots of the Aria Automation node(s) before making any changes.
Procedure
- Create a CNAME DNS Record pointing to the existing VIP FQDN, a new certificate, and import it in the Aria Suite Lifecycle locker.
Note: Per the product documentation, the new certificate SAN should list the FQDNs of the three cluster nodes and the IP addresses of the nodes. Additionally, it should list the VIP IP address, its FQDN (old name), and the new FQDN of the DNS alias record (CNAME). It is not required to change the reverse DNS PTR record.
- If SSL is terminated on the load balancer (L7 Mode), manually replace the certificate on this interface.
- SSH into any appliance in the cluster. Run
vracli load-balancer set CNAME
Note: This step also updates the vIDM client registration.
- In Aria Suite Lifecycle, run the Replace Certificate Day 2 Operation for the Aria Automation 8.x environment:
Note: This step restarts the cluster. No need to additionally run /opt/scripts/deploy.sh
- In vIDM Workspace One Application Catalog, update the application target URL in the app catalog on VMware Identity Manager.
- Login to vIDM.
- Switch to the Administration Console followed by: Catalog > Web Apps > Select the Automation instance > Edit > Modify Target URL to reflect the new CNAME FQDN.
- In Aria Suite Lifecycle run Trigger Inventory Sync for the VMware Aria Automation 8.x environment.
Note: This will update the Cluster VIP FQDN value for Aria Automation within the Aria Suite Lifecycle environment.