Backing up a Native Key Provider fails when accessing via IP

Products

• VCF Operations/Automation (formerly VMware Aria Suite)
• VMware vSphere ESXi
• VMware vCenter Server 7.0

Issue/Introduction

Symptoms:

• Attempting to back up a Native Key Provider when accessing vCenter using IP address instead of FQDN fails silently
• The key provider remains in "Not backed up" state

Environment

VMware vSphere 7.0.x

VMware vCenter Server Appliance 7.0.x

Cause

This issue is caused because of browser security. The browser checks the origin of the code that generates the backup file and compares it with the URL. This does not match because one uses FQDN, and the other uses an IP.

Resolution

This is a known issue affecting vCenter Server 7.0 U2 and is resolved in 7.0 U3.

Workaround:
To workaround this issue, access vCenter using a fully qualified domain name instead of IP address.

Additionally, if the Hostname within the VAMI is short, update the hostname to FQDN.

1. Access the vCenter's VAMI page on port 5480 via root.
2. On the left-hand side panel, navigate to the Networking section.
3. In the Network Settings view, click on Edit at the top right.
4. In the Edit Network Settings wizard:
   1. Select Network Adapter > Select the appropriate Management Network NIC > Click Next.
   2. Edit settings > Update the Hostname from short to FQDN > Click Next.
   3. SSO credentials > Enter in the SSO administrator credentials > Click Next. 
   4. Ready to complete > Review the settings before completing the wizard > Check the box to acknowledge > Click Finish.
      • Note: Reconfiguring the NIC 0 management network adapter will cause vCenter Server downtime, and it may take some time for the system to become fully operational again.
      • If downtime is not an option, you can add the vCenter FQDN via the command line by referring to steps in KB-"An error occurred while sending an authentication request".
      • Important: The steps outlined in this article require stopping the vCenter UI Service. However, this process will not impact any running VMs or hosts in the environment.

Note: - If the vCenter Version is 7.0 U3 Version and still facing the issue, then make sure to login via [email protected] and not with any AD User credentials and retry the  Native Key Provider backup.