Configuring Aria Automation Integration fails with the error below:
Unable to login to VMware Aria Automation system using provided credentials
In /storage/log/vcops/log/collector.log the error below can be seen:
Line 7386: 2025-09-24T10:31:43,875+0000 ERROR [TasksManager-TaskHandler-87723] com.vmware.adapter3.cas.util.CASAdapterUtil.handleResponse - Error connecting to CAS for URL =https://cloud.example.com/csp/gateway/am/api/login response is, response code is 404Line 7387: 2025-09-24T10:31:43,876+0000 ERROR [TasksManager-TaskHandler-87723] com.vmware.adapter3.cas.impl.CASAPIService.login - Unable to get the authentication token from VMware Aria AutomationLine 7415: 2025-09-24T10:32:11,216+0000 ERROR [TasksManager-TaskHandler-87725] com.vmware.adapter3.cas.util.CASAdapterUtil.handleResponse - Error connecting to CAS for URL =https://cloud.example.com/csp/gateway/am/api/login response is, {"timestamp":1758709930632,"type":"CLIENT_ERROR","status":"400 BAD_REQUEST","error":"Bad Request","serverMessage":"REST error received:
{ \"error\": \"invalid_grant\", \"error_description\": \"Invalid username or password\"}, status code: 400 BAD_REQUEST"} response code is 400Line 7416: 2025-09-24T10:32:11,216+0000 ERROR [TasksManager-TaskHandler-87725] com.vmware.adapter3.cas.impl.CASAPIService.login - Unable to get the authentication token from VMware Aria Automation
Aria Operations 8.18.x
Aria Automation 8.18.x
The issue occurs when using the FQDN for one of the Aria Automation nodes instead of the Load Balancer's FQDN.
Integrating Aria Automation behind a load balancer to Aria Operations use the Load Balancer's FQDN.