Expanding the vSphere vCenter Server plugin inventory directly within the Aria Orchestrator client also shows the same InvalidLogin error.
The "Update a vCenter Server instance" workflow completes successfully, but the connectivity issue persists, and workflows/inventory browsing continues to fail.
Environment
Aria Automation 8.x
Cause
This behavior is by design under specific authentication configurations. The InvalidLogin error arises because of Mismatched Identity Providers, in setup as listed below:
vRo identity provider is vCenter "A" and affected vCenter "B" connection is configured for "session per user" and expects a specific authentication token issued directly by its own vSphere SSO (Single Sign-On) service.
The Orchestrator Identity provider is the Aria Automation and vCenter "B" is configured for "session per user"
Resolution
To resolve this issue, you must configure the vSphere vCenter Server to use a "shared session" instead of a "session per user." This tells the plugin to maintain a single, shared authenticated session with vCenter, bypassing the per-user token expectation.
Procedure:
Access Aria Orchestrator Client: Log in to your Aria Orchestrator client.
Navigate to vCenter Workflows: Go to the "Workflows" tab (or "Library" > "vCenter" in older clients).
Locate "Update a vCenter Server instance" workflow: Find and run the workflow titled "Update a vCenter Server instance".
Select vCenter Instance: Choose the specific vCenter Server instance that is experiencing the InvalidLogin error.
Disable "Session per user": In the workflow's input form, uncheck the checkbox labeled "Session per user".
Submit the Workflow: Run the workflow with this change.
Verify Connectivity: After the workflow completes, verify that workflows now run successfully and that the vCenter plugin inventory can be browsed without the InvalidLogin error.