The Secure Browser client allows users to access web content published from the BYOD Gateway. This access is broken into two classifications.
- Proxied link to resources
- Non-Proxied link to resources
Proxied link refers to resources the client can only access within the company network. In order for a user to access these resources, the request will need to be proxied through the BYOD Gateway. The BYOD Gateway provides an Intranet Tunneling service that acts as an intermediary for requests from the Secure Browser seeking resources from Intranet sites or services. The Secure Browser connects to the BYOD Gateway requesting a connection to other resources available to the BYOD Gateway. The BYOD Gateway evaluates the request according to its policy rules. If the request is validated by the policy, the BYOD Gateway provides the resource by connecting to the relevant server and requesting the resource on behalf of the client.
Note: Resources requested through the BYOD Gateway ProxyConnector must be available to the BYOD Gateway directly. Check to make sure the machine hosting the BYOD Gateway can access this content without requiring a connection through a proxy server.
The BYOD Gateway Control Panel allows the administrator to configure access to these Intranet resources using the stock connector named ProxyConnector. See Tutorial - Intranet Tunnel for more information on configuring a Proxied resource.
Non-Proxied link refers to resources the client can access directly over Wi-Fi or other network connection available to the device. This is commonly used to access publicly available resources not hosted behind the company firewall. These can be company sites available in a DMZ or Cloud, or may be public sites such as salesforce.com or quickbooksonline.intuit.com. If the user has access to reach the public resource, the BYOD Gateway will allow the client to access the resource directly. The content is still encrypted on the device and any cached data is maintained within the Secure Browser container. Since the site is publicly available the request is simply not sent through the BYOD Gateway to avoid the unnecessary intermediated connection.
Any resource not listed in the BYOD Gateway policy that defines “Hosts to which the gateway may provide proxy access”, shown in the above tutorial, is treated as a non-proxied link.
Kaseya BYOD Suite