Aria Operations Login fails with "404 Page Not Found" when Integrated with vIDM

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Users are unable to log into VMware Aria Operations (formerly vRealize Operations Manager) through vIDM (VMware Identity Manager, now VMware Workspace ONE Access) and encounter a "404 Page Not Found" error. The error message explicitly states: "The page you were looking for is not available. You may need to contact your administrator with this error: 404 Page Not Found". Manual login directly to the Aria Operations UI using local credentials or other configured authentication sources works correctly, indicating the issue is specific to the vIDM integration.

Environment

VMware Aria Operations 8.x

Cause

The root cause of this issue is an incorrect configuration of the "Redirect FQDN/IP" setting within the Aria Operations vIDM integration. This setting, which dictates where vIDM should redirect the user's browser after successful authentication, is erroneously pointing to the vIDM load balancer's FQDN or IP address. For proper integration and successful redirection back to the Aria Operations UI, this setting must be configured with the FQDN or IP address of the Aria Operations instance itself, or its load balancer if one is in use. When the redirect points back to vIDM, the Aria Operations application cannot find the expected context, resulting in the 404 error.

Resolution

To resolve this issue, the "Redirect FQDN/IP" setting within the Aria Operations vIDM integration must be corrected to point to the FQDN or IP of the Aria Operations instance or its load balancer.

Access Aria Operations UI: Log in to the Aria Operations UI using an account that can bypass the vIDM integration (e.g., local admin account).

Navigate to Authentication Sources: Go to Administration > Control Panel > Authentication Sources.

Edit vIDM Configuration: Locate the configured vIDM authentication source and click on the "Edit" (pencil) icon.

Verify/Correct Redirect FQDN/IP: In the vIDM configuration settings, identify the field for "Redirect FQDN/IP".

Enter Correct Value: Change the value in this field from the vIDM load balancer's FQDN/IP to the FQDN or IP address of your Aria Operations load balancer or the primary Aria Operations node (if not using a load balancer for Aria Operations).

Save Changes: Save the updated configuration.

Test Login: Attempt to log into Aria Operations again via vIDM to confirm the issue is resolved.

Additional Information

This issue typically arises during initial setup or after environmental changes (e.g., changes in load balancer configurations, IP addresses, or FQDNs). Always ensure that the "Redirect FQDN/IP" in Aria Operations accurately reflects the access point for Aria Operations itself, not for vIDM.