Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Changing the proxyPattern on a Horizon Cloud Pod's Unified Access Gateway to Fix Identity Manager Connector Sync Issue (70986)

Last Updated: 2/28/2020Categories: How toTotal Views: 2488Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

VMware has discovered a security vulnerability between VMware Horizon Cloud Service on
Microsoft Azure and VMware Identity Manager Connector, which is a component of VMware
Identity Manager that synchronizes the Horizon Cloud resources and entitlements. This security
vulnerability only occurs when the Horizon Cloud Virtual Apps Collection, which is managed in
the VMware Identity Manager interface, is configured to point or synchronize with VMware
Horizon Cloud Service on Microsoft Azure via the External or Internal Gateway (UAG) FQDN.

Resolution

The email has been sent to customers as VMware Horizon Cloud Service on Microsoft Azure, Security vulnerability with VMware Identity Manager (IDM) Connector synchronizing through the Unified Access Gateway(UAG)

Workaround

You will need to create a client VM (any windows VM) in Azure under the same management subnet as the UAG VM.

The management subnet could be a custom one or in the format vwm-hcs-{podID}-mgmt. You can find the subnet name on the pod details page in the Administration Console.

Retrieve the UAG IP and password. You must request the VMware support team to enable retrieval of those.

Repeat the below steps for all instances

From the client VM, you can access the Admin UI with a browser at https://{UAG_IP}:9443/admin

You will need Chrome, because IE breaks sometimes

The user name is admin, the password is same as the UAG API password (see below)

Click on Configure Manually

Click on Show next to the Edge Server Settings

Click on the gear icon next to the Horizon settings

Click on more and find the proxyPattern setting.

Change the proxy pattern to :
(/|/view-client(.)|/portal(.)|/appblast(.)|/images/|/appimage(.)|/admin/SAML/metadata|/dt-rest(.)|/xmldata(.)|/sdk(.*))

Click on save

Note the setting will change with the next upgrade.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

HorizonService-Azure-IDM_UAG-Security-Email-Final

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Intel® Optane™ DC 永続メモリ モジュールをサポートする Intel® Server System S2600WF ファミリ (70884)

KB
•
PMEM が構成された大規模な仮想マシンを削除すると、vCenter Server で実体なしの状態になる (71099)

KB
•
使用 HPE Nimble Storage Peer Persistence 实现 vSphere Metro Storage Cluster (vMSC) (77185)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon Cloud on Microsoft Azure

Related Versions:

Take Our Survey

Support Assistant