This is a known issue affecting VMware vRealize Automation (formerly known as VMware vCloud Automation Center for Server) 6.2.
Currently, there is no resolution.
To work around the issue, ensure that the hostname of the vRealize Automation (formerly known as VMware vCloud Automation Center for Server) Identity Server matches the name that was entered in the initial appliance installation:
- Log in to the vRealize Automation (formerly known as VMware vCloud Automation Center for Server) Identity Server and navigate to Network
- Update the HostName to match the name entered at initial vRealize Automation Identity appliance installation
- Click the Save
- Re-attempt to initialize the SSO