VMware Cloud Community
christianpg
Enthusiast
Enthusiast
Jump to solution

vCAC 5.2 integration with external vCD. Proxy configuration needed?

Hi there.

I have a DEM-W talking to Internet via web proxy.

For the Amazon EC2 endpoint, the web proxy was part of the configuration and is working fine.

My endpoint for the external vCloud Director platform does not work, though...

Both connections are from the same DEM-W.

Error message:

Workflow "vCloudEndpointDataCollection" failed with the following exception:

System.ArgumentException: Cannot connect to vCloud serverUrl:https://<correct url>, userName:<correct username>, org:<correct org> Please verify endpoint and credentials.

Do I need to specify the web proxy for this endpoint?

How?

It doesn't feel right to specify the web proxy for DynamicOps.DEM.exe.config's basicHTTPBinding.

Then all local communication would go via the proxy as well, right?

Reply
0 Kudos
1 Solution

Accepted Solutions
christianpg
Enthusiast
Enthusiast
Jump to solution

Seeing that the basicHttpBinding on DynamicOps.DEM.exe.config had the setting useDefaultWebProxy="true" I realized something...

Even with proxy config set for my admin user and WinHTTP, it was not set for the service account used by the DEM-W.

Logged in as service account, updated proxy config and presto...

The follow-up question is: why are these two endpoints (EC2 & vCD) handled so differently by the same DEM-W?

View solution in original post

Reply
0 Kudos
3 Replies
christianpg
Enthusiast
Enthusiast
Jump to solution

I have noticed that the Amazon EC2 endpoint as well as the vCD endpoint are stored in DB table ManagementEndpoints with additional info in ManagementEndpointProperties.

Since these are both handled by the DEM-W, would it just work if I replicated the ManagementEndpointProperties for the EC2 proxy config (named __Proxy.) created new UIDs and associated them with the vCD endpoint?

Even if it could work, it would still be a hack. Any other ways to solve this?

Using the web service managementmodelentities would basically give me the same result...

Reply
0 Kudos
christianpg
Enthusiast
Enthusiast
Jump to solution

Tried the following SQL inserts to add proxy config to my vCloud Director endpoint using the same proxy credentials as my EC2 configuration

insert into [vCAC].[dbo].[ManagementEndpointProperties]     (Name,Value,ManagementEndpointID,ManagementEndpointPropertyID)
values ('__Proxy.Address','144.177.35.107','99EEE15C-1703-44CE-90F1-84CFA12C70B4',NEWID());

insert into [vCAC].[dbo].[ManagementEndpointProperties]     (Name,Value,ManagementEndpointID,ManagementEndpointPropertyID)
values ('__Proxy.Port','8080','99EEE15C-1703-44CE-90F1-84CFA12C70B4',NEWID());

insert into [vCAC].[dbo].[ManagementEndpointProperties]     (Name,Value,ManagementEndpointID,ManagementEndpointPropertyID)
values ('__Proxy.CredentialId','080787c9-8585-4609-91a5-f503ac28ae88','99EEE15C-1703-44CE-90F1-84CFA12C70B4',NEWID());

Via wireshark I could see that the DEM-W ignored my proxy config and continued to contact via TCP 443...

Reply
0 Kudos
christianpg
Enthusiast
Enthusiast
Jump to solution

Seeing that the basicHttpBinding on DynamicOps.DEM.exe.config had the setting useDefaultWebProxy="true" I realized something...

Even with proxy config set for my admin user and WinHTTP, it was not set for the service account used by the DEM-W.

Logged in as service account, updated proxy config and presto...

The follow-up question is: why are these two endpoints (EC2 & vCD) handled so differently by the same DEM-W?

Reply
0 Kudos