The page loaded correctly and HTML access /w Blast was working perfectly. (/|/view-client(.*)|/portal(.*)|/downloads(.*))Īnd, Viola! That fixed the reverse proxying issue with View 2203 UAG.
When I could see from the logs proxying was not working, I changed the proxy pattern setting to the following: On version 2006 of the UAG the following proxy pattern was configured: No proxying rules for http request GET /portal/nativeclientīit of a dead give away here that something wasn’t quite right with the new UAGs proxy pattern setting! No proxying rules for http request GET /portal/favicon.ico?v=19431065 No proxying rules for http request GET /portal/webclient/icons-19431065/icon_html_access.svg No proxying rules for http request GET /portal/webclient/icons-19431065/ I was sat scratching my head on this one for a while, when I finally checked esmanager.log in the UAG – specifically the I was able to see that proxying for the assets and images of the connection server were giving the error ‘No proxying rules for http request’: At first everything was sweet (all working via the horizon client), however the UAG upgrade broke the reverse proxying of assets such as the view splash page and HTML access login. The current UAG version is 2203 – I was upgrading from 2006. When it came time to upgrade the Unified Access Gateways, the simplest way is to just deploy the new OVA and export the settings from the existing and then import them to the new one.
Remember to add in sha1= before pasting in the actual thumbprint.I recently went through a VMware View upgrade from branch verison 2006 to 2111. Under Thumbprint, you can just copy the text. If you don’t know the thumbprint, you just need to launch a browser, navigate to the admin page and view the details of the certificate. Under Horizon Settings, you will find an area to enter in your Thumbprint. You will need to update the thumbprint configuration in the UAG. There is ONE additional step you will need to preform though if you want a successful connection between the UAG and the connection server. Couple of clicks and you will be on your way. Inside the UAG interface, there is an option to upload certificates via the browser. Upgrading certificates in the UAG is very easy. Now that the admin console is up to date and can access the administrative console, it is time to move to the UAG portion of the connection. This will give the server the necessary pieces of the puzzle to provide clients with a secure connection end to end. The quick and easy fix to this issue is to just reexport your PFX key with it’s Private key and then on re-import, check the export private key option.
0 kommentar(er)
