Adding vCenter instance to vRO looks unhealthy - (unusable: java.lang.ClassCastException: com.vmware.vcac.authentication.http.spring.oauth2.OAuthToken cannot be cast to com.vmware.vim.sso.client.SamlToken)

-




Issue : 

 Adding vCenter instance to vRO completes but the inventory has below messages.

https://vcenter.wecloud.lab:443/sdk (unusable: java.lang.ClassCastException: com.vmware.vcac.authentication.http.spring.oauth2.OAuthToken cannot be cast to com.vmware.vim.sso.client.SamlToken)




Storage Policies (unusable: PBM error: java.lang.RuntimeException: java.lang.ClassCastException: com.vmware.vcac.authentication.http.spring.oauth2.OAuthToken cannot be cast to com.vmware.vim.sso.client.SamlToken)



Storage Policy Components (unusable: PBM error: java.lang.RuntimeException: java.lang.ClassCastException: com.vmware.vcac.authentication.http.spring.oauth2.OAuthToken cannot be cast to com.vmware.vim.sso.client.SamlToken)

Resolution : 

Add the vCenter instance as Share a unique session



Hope it helps :)

Comments

  1. AnonymousJanuary 15, 2021 at 3:49 PM

    Thanks very much for the solution. We have migrated to VRO 8.2 and we also faced this problem! This was solved immediately

    ReplyDelete
  2. AnonymousNovember 17, 2021 at 5:51 PM

    Thanks it works even on VRO 8.6 !

    ReplyDelete

Post a Comment

Popular posts from this blog

vCloud director 9.7 appliance deployment step by step guide

-
Image
With the new vCloud director releasing and making it full appliance with embedded vpostgres, I though I will put up a post with the complete installation guide. There have been some challenges in the getting the deployment successful. Prerequisite : Reverse DNS proxy must be configured for the eth0 ipaddress. This is to get the correct hostname for the appliance.  The NFS share is setup for the VCD transfer directory. It is recommended to have the eth0 and eth1 in different subnets. eth0 is for the vcd cell and eth1 is for the vPostgres .The reason for the having 2 subnets is to avoid duplicate entries in the route table.  Installing vCloud director step by step guide :  I should ideally be using different submets as per the VMware documentation but since I do not have a different portgroup setup, I am going with the same subnet.  As mentioned in the prereq section, the reason for the having 2 subnets is to avoid duplicate entries in the route tab
Read more

How to Install and Uninstall Guest agent for vRA Windows machines

-
Image
Connect to the vRA appliance using the IP or hostname  Choose the appropriate setup for your Windows server  Extract the files to C:\VRMGuestAgent\ . In my case, I have already extracted it.  Before you install the guest agent download and install the IAAS manager server certificate into the windows machine  Save the file as Cert.cer  Install the Cert into the Local machine and Trusted root store Rename the cert.cer to cert.pem and move it to folder C:\VRMGuestAgent\ Now, copy the certificate file into the vRMGuestAgent Extracted folder  Open the command prompt as admin and navigate to C:\VRMGuestAgent. In this case 192.168.2.15 is my Manager server . The default port is 443.  You will see the Guest agent service in the services list. Manually start the service.  Your windows guest agent is installed :)  How to Uninstall Guest agent on windows machine  To uninsta
Read more

VM console fails to connect - vCloud director 9.7

-
Image
I deployed a new vCloud director 9.7 and the VM console fails to connect even though the certificates and URLs are updated correctly in Public Addresses. The chrome browser console (ctrl+shift+j) fails like below :  failed: Error during WebSocket handshake: Unexpected response code: 404 After reading the VMware documentation which says " For an installation with a single IP address, you can customize the console proxy address from the  vCloud Director  Web Console. For example, for the  vCloud Director  appliance, you must customize the console proxy address to  vcloud.example.com :8443 " From vCloud director 9.7, the second network (eth1) is dedicated to vpostgres database and console proxy uses (eth0) with a custom port 8443 Fix :  Update the console proxy address with custom port 8443 under vCD portal --> Administrator --> Public addresses Tadaa!  Thanks for reading. Hope it helps :) 
Read more