The ETP mobile client extends ETP protection to mobile devices. You deploy the mobile client in your enterprise to scan mobile traffic and enforce ETP policy to mobile applications.
The following applies:
- Administrators configure the same policy settings and ETP Client configuration settings for the mobile client as they do for the desktop version. For example, you can configure the setting that allows end users to disable the client.
- The mobile client is supported on Android, Apple iOS, iPadOS, and Google Chrome OS. For more information about supported operating systems and devices, see Supported mobile operating systems.
- The ETP mobile client is available in the app stores specific to the device and operating system. You can use your organization’s device management (MDM) solution to deploy the client from app stores to supported mobile devices across your network.
- You must use an entitlement code to activate ETP mobile clients that are distributed with Mobile Device Management (MDM) solutions. For instructions, see Distribute ETP mobile clients with Mobile Device Management (MDM).
- End users can activate the mobile client on their personal device with an activation code. For more information, see Bring your own device (BYOD) support.
- If you plan to allow MITM TLS Inspection by ETP Proxy, you can use your organization’s MDM solution to distribute the ETP Proxy TLS man-in-the-middle certificate to your mobile devices.
After the ETP mobile client is installed and set up on a user’s device, it acts as a VPN client. ETP Client protects user’s devices whether it is on a wireless network or the cellular network. By default, ETP mobile client disables itself when another VPN client is enabled. To avoid this, you must configure the MDM solution to restrict use of VPN clients and prioritize the ETP Client.
Note: ETP mobile client now supports mobile network operators and internet service providers that use only IPv6 in their network.