Using VMware Browser for VMware Tunnel controls how the end users access internal sites by configuring communication between the application and the VMware Tunnel. Once configured, access to URLs you specify (using VMware Browser) goes through the VMware Tunnel.
Consider using VMware Browser with the Per-App Tunnel component of VMware Tunnel. The Per-App Tunnel component provides better performance and functionality than the Proxy component. VMware Browser with the Per-App Tunnel component does not require additional configuration.
If you are using VMware Browser with the VMware Tunnel with Proxy component:
- Navigate to Groups & Settings > All Settings > Apps > Settings and Policies > Security Policies.
Select Enabled for AirWatch App Tunnel and specify the App Tunnel Mode as VMware Tunnel – Proxy.
- (Optional) Enable the split tunnel for iOS devices by entering URLs into the App Tunnel Domains text box. If a URL that is about to be invoked contains a domain that matches the list in the settings, this URL request goes through the VMware Tunnel. If the URL domain does not match the domain in the list, it goes directly to the Internet. Leave the text box empty to send all requests through the VMware Tunnel.
- Select Save.
- Ensure the VMware Browser is using the Shared SDK profiles for iOS and Android by navigating to Groups & Settings > All Settings > Apps > VMware Browser and selecting them under SDK Profile.
Caveats and Known Limitations
For VMware Tunnel, the current authentication scheme requires the use of a chunk aggregator of fixed size. A low value puts restrictions on the amount of data that is sent from the devices in a single HTTP request. By contrast, a high value causes extra memory to be allocated for this operation. Workspace ONE UEM uses a default optimum value of 1 MB, which you can configure based on your maximum expected size of upload data. Configure this value in the proxy.properties file on the VMware Tunnel server in the /conf directory.