VMware Unified Access Gateway 3.9 Compatibility Notes Doc VMware What is New in This Release VMware Unified Access Gateway 3.9 Release Notes Docs VMware For more detail please visit VMware Product Interoperability Matrices page. As of released date, version 3.9 is supported for Horizon 7 version 7.5 to 7.12. New version of VMware Unified Access Gateway (UAG) 3.9 has been released on 17 March 2020. local, DNS, Horizon, uag, unified access gateway, VMware local domain to the domains there.Īt last I rebooted the appliance and was able to configure RSA on the UAG’s. Edit /etc/systemd/nf and uncomment the domains line and adding in your. Fortunately there is a way to fix this issue. It appears that the new systemd-resolved method uses. After searching the internet for this issue I found the following article:
The log shows that the service is unable to resolve the names of the RSA appliances. Authbroker.log is located at /opt/vmware/gateway/logs. This file contains log messages from the AuthBroker process, which handles Radius and RSA SecurID authentication.
In the documentation of the UAG’s I found that are is an authbroker.log logfile on the applicance. This message says nothing to me, so I had to troubleshoot this issue. After this I tried to setup the RSA configuration manually but it showed on error “unable to save configuration”. This shows that RSA authentication is not configured. I deployed the OVA, exported and imported the JSON and then I checked the admin interface. The RSA applicances of this customer are part of a. I was unable to setup RSA authentication on the Unified Access Gateways. local domain.Īt one of our costumers I was asked to upgrade their VMware Unified Access Gateways from version 3.5 to 3.8. This is a small blog post on solving a DNS issue with the VMware Unified Access Gateway version 3.7 and above when using a.
0 kommentar(er)
