Troubleshooting initial deployments of VMware Aria Orchestrator 8.x after configuring the Authentication provider with shortname or IP address

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• You have recently deployed VMware Aria Automation Orchestrator 8.x (formerly VMware vRealize Orchestrator).
• You have configured the Authentication provider using the vCenter IP address or shortname.
• You see following or similar warning messages in the Control Center logs

  020-06-10 13:01:04.844+0000 [localhost-startStop-1] WARN {} [ComponentManagerSsoLookupService] Could not get Sso Endpoint information through service call. Fall back to local settings.
  com.vmware.o11n.cis.CisException: com.vmware.o11n.cis.CisException: com.vmware.o11n.cis.CisException: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative names matching IP address xx.xx.xx.xx

Environment

VMware Aria Automation Orchestrator 8.x
VMware vRealize Orchestrator 8.x

Cause

When deploying the VMware Aria Automation Orchestrator 8.x appliance, you must set a host address in the Authentication configuration in Control Center. A TLS check is performed at this time and the configuration of this host address must match to the vCenter certificate common or subject alterative name fields during the TLS negotiation process.

Resolution

Procedure

1. Login to VMware Aria Automation Orchestrator Control Center interface.
2. Select Configure Authentication Provider click Unregister (without providing a password) from the configured authentication provider host address.
3. Reconfigure the authentication provider using the FQDN of the vSphere endpoint.
4. Wait for a few minutes for the application to start.
5. Verify you can now login to VMware Aria Automation Orchestrator 8.x

Additional Information

Impact/Risks:
VMware Aria Automation Orchestrator 8.x fails to start properly and is inaccessible.