VMware Horizon Community
EagleB5
VMware Employee
VMware Employee
Jump to solution

How to make Horizon View Connection Server use a Proxy Server

Hi all,

We have an issue with our Horizon View Connection Servers. Eventhough they have been configured with "netsh winhttp set proxy" to use our proxy server, the Horizon services won't. We also configured our local system account to go through the proxy for internet connection and guess what, the Horizon services won't. However the services all running as local system.

We just wantet do activate SAML authentication on our View Connection Servers with the appropriate URL like: https://<YOUR HORIZON SERVER NAME>/SAAS/API/1.0/GET/metadata/idp.xml

If we start a browser as local system and connect to this URL it works. If we try to configure SAML with the exact same URL on our Connection Server it won't. It don't event connect to the proxy, no request is coming.

Does anybody have an idea how to solve this issue? Make Horizon View services use of the configured proxy server?

Thank you,

Tags (3)
1 Solution

Accepted Solutions
RoderikdeBlock
Enthusiast
Enthusiast
Jump to solution

Horizon 7 provides proxy support for the VMware Identity Manager (vIDM) server. The proxy details such as hostname and port number can be configured in the ADAM database and the HTTP requests are routed through the proxy.

This feature supports hybrid deployment where the on-premise Horizon 7 deployment can communicate with a vIDM server that is hosted in the cloud.

Prerequisites

Procedure

Start the ADSI Edit utility on your Connection Server host.

  1. Expand the ADAM ADSI tree under the object path: cd=vdi,dc=vmware,dc=int,ou=Properties,ou=Global,cn=Common Attributes.
  2. Select Action > Properties, and add the values for the entries pae-SAMLProxyName and pae-SAMLProxyPort
Roderik de Block


Blog: https://roderikdeblock.com

View solution in original post

3 Replies
RoderikdeBlock
Enthusiast
Enthusiast
Jump to solution

Horizon 7 provides proxy support for the VMware Identity Manager (vIDM) server. The proxy details such as hostname and port number can be configured in the ADAM database and the HTTP requests are routed through the proxy.

This feature supports hybrid deployment where the on-premise Horizon 7 deployment can communicate with a vIDM server that is hosted in the cloud.

Prerequisites

Procedure

Start the ADSI Edit utility on your Connection Server host.

  1. Expand the ADAM ADSI tree under the object path: cd=vdi,dc=vmware,dc=int,ou=Properties,ou=Global,cn=Common Attributes.
  2. Select Action > Properties, and add the values for the entries pae-SAMLProxyName and pae-SAMLProxyPort
Roderik de Block


Blog: https://roderikdeblock.com
EagleB5
VMware Employee
VMware Employee
Jump to solution

Thank you very much! With all googeling we missed this part...

Spagna
Contributor
Contributor
Jump to solution

Hi, my customer have those entries because previously they use the proxy

they have "blanked" the values, but we have issues on communicating to trust a public certificate for the metadata and the SAML of WS1 access.

Is it possible that by removing those entries,pae-SAMLProxyName and pae-SAMLProxyPort, the system turnback to work as expected?

Thanks in advance

Fabio

Reply
0 Kudos