vCenter endpoint in Aria Orchestrator is in unusable state
Article ID: 343875
Updated On:
Products
Issue/Introduction
- Newly added vCenter server is in an unusable state.
- You see an error on vCenter server endpoint in Aria Orchestrator:
(unusable: java.lang.RuntimeException: Do not know how to handle token of type class com.vmware.o11n.security.csp.CspExpiringAuthenticationTokenAdapter)
( or )
https://<vCenter_FQDN>:443/sdk (unusable: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException)
( or )
https://<vCenter_FQDN>:443/sdk (unusable: invalid login)
- Your Aria Orchestrator authentication mode is set to VMware Aria Automation.
- Your vCenter server endpoint is configured in 'session-per-user' mode in Aria Orchestrator.
Environment
VMware vRealize Orchestrator 8.10.x
VMware Aria Automation Orchestrator 8.12.x
Cause
In Session per User mode, the Orchestrator client retrieves credentials from the user who is logged in. As the token is generated by Aria Automation, vCenter server is unable to handle it resulting in the error.
Resolution
To resolve the issue, update vCenter server endpoint to use Shared session mode:
- Login to Aria Orchestrator client.
- Navigate to Update a vCenter Server instance workflow and click Run.
- Select the affected vCenter server instance and click the Update the log-in properties tab.
- Uncheck the Update the method to manage user access to the vCenter Server system. If you select No, Orchestrator will create only one connection to vCenter Server (the method is share a unique session) checkbox.
- Update the user name and password and click Run.
The endpoint is updated.
Note: If these steps are not enough, please use the Remove a vCenter instance followed by Add a vCenter instance to recreate the instance.
Additional Information
In step 4 above, newer versions (8.18.1) will state:
Do you want to create a session per user to the vCenter Server? If un-checked, Automation Orchestrator will create a shared session (single connection) to the vCenter Server.
Feedback
