Showing posts from January, 2020

How to connect to vCloud director using REST API clients ?

We all have had the use case to connect to vCloud director via API to pull some details. Below is the detailed process on how to connect using REST client.

I am using the Postman windows client. The procedure will remain the same for the other REST client applications too.

Step 1 :

Download the postman client

Step 2 (Optional) : 

You may have to disable the SSL certificate verification if you are trying this on a test environment and do not have trusted certificates

Step 3:

Enter the credentials under the Authorization tab You must append either @system to the username or @orgname. This depends on the role you have. As a system administrator, you must use @system because your admin user is not bound to a special organization. As org admin or org user, you must append your organization name.

For example: administrator@system or orgadmin@wecloud

Enter the Accept header under the Headers tabsKey : Accept  Value : application/*+xml;version=32.0
The version …

vCD HTML5 UI - Editing rights bundle fails with " Unexpected token < in JSON at position 0 "

If you have come across an error message similar to the below in the vCD HTML5 UI, the issue is due to the large payload on the load balancer

Unexpected token < in JSON at position 0

Browser console has the below error :

Failed to load resource: the server responded with a status of 502 (Bad Gateway)
service-provider.bundle.js:1 Unsupported REST exception RightsComponent#rights SyntaxError: Unexpected token < in JSON at position 0
  at JSON.parse (<anonymous>)
  at CatchSubscriber.selector (service-provider.bundle.js:1)
  at CatchSubscriber.error (vendor.bundle.js:991)
  at XMLHttpRequest.s (vendor.bundle.js:830)
  at ZoneDelegate.invokeTask (vendor.bundle.js:1040)
  at Object.onInvokeTask (vendor.bundle.js:457)
  at ZoneDelegate.invokeTask (vendor.bundle.js:1040)
  at Zone.runTask (vendor.bundle.js:1040)
  at ZoneTask.invokeTask [as invoke] (vendor.bundle.js:1040)
  at p (vendor.bundle.js:1012)

Action Plan:

In my case, I am using NSX Edge Load balancer

PUT https://<NSX-IP>/api/4.0…