Update certificate/password on vRA cloud account

-

Symptoms:-

  • vCenter Server Cloud Account username or password has been changed.
  • An existing endpoint in VMware vRealize Automation (Now VMware Aria Automation) needs to be updated with the new credentials.
  • Credentials validation is successful, but then you see the error:
Failed to connect to vCenter: Error: Cannot login due to incorrect username and password
  • The configuration fails to load and the endpoint cannot be saved.
  • Data collection and provisioning to this endpoint fails due to the invalid credentials.

 

1. Log in to vRA, Right-click anywhere, and click on Inspect.


Click on Network tab and press CTRL+R


3. Scroll a bit down and search for Access-Token Row and click on it and navigate to the Response section.



4. Browse to Swagger API from API Documentation and click on Authorize button.





5. Enter Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxx (here xxxxxxxxxx is the Access Token you copied) and hit Authorize.



6. Post performing this - Swagger is now Authorized to vRA and you can use API calls.

7. Press Ctrl + F and search for "Update vSphere cloud account".



In the body pass the following (with proper inputs for hostname, certificate info, password & username) and execute it:

 
{
  "hostName": " ",
  "certificateInfo": {
    "certificate": " -----BEGIN CERTIFICATE-----\nMIIExxxxxxxxxxxxxxxxxxxxxCwUAMIGkMQswCQYD\nVQQDDAJDQTEXMBUGCgmSJomT8ixkARkWB3Zzxxxxxxxxxxxxxxxxxxxxxxb3JuaWExJjAkBgNV\nBAoMHWNhdmEtNi0wMDEtMTQwLmVuZy52bXdhcmUuY29tMRswGQYDVQQLDBJWTXdh\ncmUgRW5naW5lZXJpbmcwHhcNMjMwNDI4MDAzODUyWhcNMjUwNDI3MTIzODUyWjAk\nMRUwEwYDVQQDDAwxMC4yMjUuMS4xNDAxCzAJBgNVBAYTAlVTMIIBojANBgkqhkiG\n9w0BAQEFAAOCAY8AMIIBigKCAYEAvB1xuJbc9dg5WOzt3+th2/rq/Kku6mmkeaBJ\nCKetYbt21QYLEMJ68GFuU9Q/RCs0DiDCmWR3APYxBbL9Hp7cB6PAMkR5PEoQCaHA\nXXJsw3TFPbU8LVmq/VMibAuNGo++4emfUNGGX2PJm5F1S7sPadODGxxxxxxxxxxxxxxxxxxxxxxxxxxxxO9z+/NuAXnXVJwlA==\n-----END CERTIFICATE-----\n "
  },
  "password": " ",
  "username":" "
  }
 
 
 

Ssh to any vRA node appliance and run the below command to get the vCenter certificate info and grab that to run the API above:

 
openssl s_client -connect <vCenterHostname>:443 2> /dev/null | openssl x509 | awk 'NF {sub(/\r/, "");  printf "%s\\n",$0;}'
 
 
 

Grab the certificate starting from "-----BEGIN CERTIFICATE-----\nM" and till "-----END CERTIFICATE-----\n". 

 
 
 

You can get the cloud account id in the URL after %2F  


 


Once, all the info pasted in body, execute the API call.

Go back to vRA cloud account, refresh it and validate the account again. it should be OK now.

For more info, follow KB-https://kb.vmware.com/s/article/88531

Cheers !!



                                                                                                                    


Comments

Post a Comment

Popular posts from this blog

How to migrate the N-VDS as the host switch to VDS 7.0 in NSX-T 3.x

-
Image
  Hello There, In this article, i am covering how to migrate the ESXi host switch from N-VDS to VDS 7.0 switch in NSX-T 3.2.x version. When using N-VDS as the host switch,  NSX-T  is represented as an opaque network in  vCenter Server . N-VDS owns one or more of the physical interfaces (pNICs) on the transport node, and port configuration is performed from  NSX-T Data Center . You can migrate your host switch to  vSphere  Distributed Switch (VDS) 7.0 for optimal pNIC usage and manage the networking for  NSX-T  hosts from  vCenter Server . When running  NSX-T  on a VDS switch, a segment is represented as an  NSX-T  Distributed Virtual Port Groups. Any changes to the segments on the  NSX-T  network are synchronized in  vCenter Server. We have an NSX-T environment running with NSX-T 3.2.2.1 version. this environment was designed and implemented with NSX-T 2.x version and that time we used the N-VDS as host switch configuration on the transport nodes bcuz VDS was not supported that time. 
Read more

vROPS appliances password remediation tasks failed from SDDC manager

-
Image
Issue details:-   Password remediation tasks on SDDC manager getting failed with below error. However, we are able to connect SSH with root password on the vROPS appliances, no issues with credentials. I checked Operations logs on SDDC manager and found below logs, indicating the SSH connectivity issues from SDDC to vROPS appliances. Tried to do SSH vROPS appliance from SDDC manager, getting below error... Seems some issue with ECDSA key.. Resolution:- SSH to vROPS appliance and retrieve the ECDSA ssh keys as below. Now, we have 2 options to update the correct SSH keys for vROPS appliance on SDDC manager known_Hosts files located at below location.   /root/.ssh/known_hosts   /etc/vmware/vcf/commonsvcs/known_hosts   /home/vcf/.ssh/known_hosts   /opt/vmware/vcf/commonsvcs/defaults/hosts/known_hosts First option is manually copy and paste the SSH key on all the known_hosts files and restart the SDDC manager services and then try to remediate the password again. it will be successful this
Read more

How to Import/Register a VM into vRA portal

-
Image
You can import an unmanaged virtual machine to a vRealize Automation environment. An unmanaged virtual machine exists in a vCenter but is not managed in a vRealize Automation environment and cannot be viewed in the vRA portal . Once you import an unmanaged virtual machine, the virtual machine is managed by using the vRealize Automation management interface. you can see the virtual machine on the Managed Machines tab or the Items tab. Please follow below steps to Import/Register VM into a vRA portal. Log in to vRealize Automation as a fabric administrator and as a business group manager. If you are importing virtual machines that use static IP addresses, prepare a properly configured address pool.  If you use bulk import to import a virtual machine with a static IP address that is allocated to another virtual machine, the import fails. Create a Blueprint and should not have even network attached as well. See below snapin. Create Network profile that shoul
Read more