{ "minorErrorCode": "METHOD_NOT_ALLOWED", "message": "HTTP method not allowed", "stackTrace": "com.vmware.vcloud.api.rest.toolkit.exceptions.MethodNotAllowedRestApiException: HTTP method not allowed\n\tat com.vmware.vcloud.api.rest.providers.filters.RestApiRequestVersionCompatibilityFilter.filter(RestApiRequestVersionCompatibilityFilter.java:90)\n\tat org.apache.cxf.jaxrs.utils.JAXRSUtils.runContainerRequestFilters(JAXRSUtils.java:1918)\n\tat org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:206)\n\tat
Cloud Director 10.5 and later.
This is a known issue identified in Cloud Director 10.5 versions and later.
This is documented in the release notes available here.
This issue is caused by the API version used in the backend code. Content Hub uses Alpha APIs and Alpha APIs do not work with Multisite in provider portal.
This is resolved in a later release of Cloud Director.
The workaround for the providers is to use the API to view and manage the ContentHub and its resources. This can be done via API Explorer or Postman.
The associated API list for the ContentHub management is available here.
View ContentHub source: https://developer.broadcom.com/xapis/vmware-cloud-director-openapi/v38.0/cloudapi/1.0.0/catalogContentSources/catalogContentSourceId/get/
Create ContentHub source : https://developer.broadcom.com/xapis/vmware-cloud-director-openapi/v38.0/cloudapi/1.0.0/catalogContentSources/post/
To connect to VCD via API, please refer to the article 320526.