Unable to save updated credentials for the VCF cloud account in VMware Aria Automation

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• The cloud account will not be saved when updating the credentials and will show error:

"Unable to update account with hostname ..."

• This issue occurs because of the the issues related to Temporary use of legacy Cloud Account API or Cannot change vCenter password in VMware vRealize Automation

Environment

VMware vRealize Automation 8.x

Cause

• This issue occurs because of the the issues related to the following article : Cannot change vCenter password in VMware vRealize Automation

Resolution

• This issue has been resolved in vRealize Automation 8.8.2 and later

Workaround:

• To work around this issue you will need to update the vCF Cloud account via API call.  To do this you need to capture the API request using a developer console in a browser like Chrome.  To do this you open the Dev console and save the vCF Cloud Account.  In the network output of the console you will find the PATCH request.
• The following steps are based on using Postman and an authenticated user that has Cloud Assembly Admin Role assigned.

1. Back up your environment prior to making any changes.
2. Use this KB Temporary use of legacy Cloud Account API first to move to legacy API.
3. Generate the access token "Generate an Access Token and Bearer Token in VMware Aria Automation for API Authentication"
4. Grab the request body from the dev console and paste it into a postman PUT request to "url-home/provisioning/uerp/provisioning/mgmt/endpoints".
5. Click on the "beautify" button to clean up the request body.
6. Carefully remove any of the "certificate" properties from the request in the endpointProperties or customProperties.
7. Add "acceptSelfSignedCertificate": "true" to the request in the "endpointProperties".
8. Add "privateKey" and "nsxPrivateKey" to the request in "endpointProperties" as well. These are the passwords for vSphere and NSX
9. Now click on Send.

Additional Information

Impact/Risks:

• If there are ongoing deployments, this may cause inconsistencies or error in deployments.