Invalid Tenant Issue While Accessing Secondary vIDM Nodes URLS when the multi-tenancy is Enabled

Products

• VMware Aria Suite

Issue/Introduction

When attempting to log in to specific vIDM nodes in a cluster using individual URLs, you may encounter an "Invalid Tenant" error. However, logging in via the load balancer (LB) URL is successful. This issue particularly affects access to node-specific URLs, especially for nodes 2 and 3.

Environment

VMware Identity Manager (vIDM)

Cause

The issue is likely related to the configuration of multi-tenancy in the Aria Lifecycle Manager . When multi-tenancy is enabled, the system modifies the URLs and routing mechanisms, resulting in previous URLs becoming obsolete. This configuration changes the accessibility of nodes and directs traffic through the new VIP URL

Resolution

To resolve the issue, follow these steps:

Verify Multi-Tenancy Configuration:

• Log in to the Aria Lifecycle Manager
• Navigate to Tenant Management.
• Confirm that multi-tenancy is enabled and verify the configurations.

Use the Correct VIP URL:
        Ensure that users are accessing the vIDM environment through the correct load balancer URL
        Inform users that the previous URL is no longer in use and should not be used for accessing the vIDM nodes.

Check System Health:
        After logging in through the LB URL, check the system health dashboard to ensure that the system is functioning correctly. The system health should be good if all configurations are correct.

Access Individual Nodes:
       If accessing individual nodes is necessary, ensure that the URLs are correctly configured to recognize the tenant. However, typically, individual node access might be restricted due to multi-tenancy settings.

Additional Information

The transition to multi-tenancy involves setting up a master alias for simplified access and management.