Steps to Retrust vIDM Certificate on Aria Automation 9.x Using Script

Products

• VCF Automation

Issue/Introduction

After upgrading Aria Automation to version 9.x or higher, the vIDM certificate may need to be re-trusted to restore proper authentication and integration functionality. This article provides steps to automate the re-trust process using a shell script.

Environment

Aria Automation 9.x or later

Cause

Post-upgrade, the existing vIDM certificate may no longer be trusted by Aria Automation. This leads to authentication or communication issues between Aria Automation and vIDM. A re-trust of the updated certificate is required.

Resolution

Follow the steps below to retrust the vIDM certificate:

1. Prerequisites

• Aria Automation must be successfully upgraded to version 9.x or higher and the instance must be active.
• You must have a valid, new PEM certificate file. Ensure it is not the same as the old certificate.
• Place the new certificate file in a chosen directory on the vRLCM terminal.

Required inputs:

• VCFA hostname
• VCFA password (used to log in to the VCFA instance)
• New certificate full file path (e.g., /root/script/Certificate_wsa-new-certificate.pem)

2. Procedure

• Log in to the vRLCM instance terminal.
• Download the script attached to this KB (vIDMRetrustCertificate.sh)
• Make the script executable:
  
  chmod +x vIDMRetrustCertificate.sh
  
  
• Run the script:
  
  ./vIDMRetrustCertificate.sh
  
  
• Provide the required inputs when prompted.
• Once execution completes, log in to the VCFA instance and verify that the new certificate is successfully updated and trusted.

Additional Information

Ensure the certificate file path is accessible from the vRLCM terminal.

If the script execution fails, double-check file permissions and input values.

This script is intended only for Day 2 certificate retrust post-upgrade, not for initial deployments.