See the Downloads for links to the respective app store.
Using mobile clients
Mobile operating systems are less capable than their desktop counterparts. The mobile client looks, feels, and behaves the same as the desktop client in most respects, but some considerations apply when configuring AppGate ZTNA for mobile. Mobile operating systems expect relatively simple network configurations, so limit the number of Sites (tunnels), entitlements, and routes to maintain compatibility.
For more information about how routes are set, see Routing client traffic.
Installation using MDM
You can use Mobile Device Management (MDM) systems to install the mobile clients. AppGate follows the best practices documented by the AppConfig Community. AppConfig is a standardized method for application configuration and management on managed devices. It is compatible with a range of MDM vendors such as MobileIron and MS Intune.
As described in the Client profiles section, you can configure clients using a profile link. Users then only need to enter their username and password to connect.
You can combine these two features to set up enterprise-managed mobile devices:
On Android and ChromeOS, add a manifest restriction within the app restrictions.
On iOS and iPadOS, use managed configuration.
The AppConfig approach provides key-value pairs from the MDM. AppGate ZTNA clients look for a single key: ag_config. Clients expect a JSON structure as the value for that key. The JSON structure must include a key named ag_url. It can also include additional parts. The first part, ag_url, comprises the client profile, which sets the URL, SPA key, certificate fingerprint, and identity provider. Additional parts can include device claims you want reported when the client connects. For example, you can pass a device claim "mdm_approved": "5e224d10-a7c0-4f3f-a72c-3d002be0730b" to verify that a connecting iOS or Android client comes from a company MDM-approved device.
App configuration
The following table describes the app configuration key:
Configuration key | Description | Value | Type | iOS support | Android for Work support |
|---|---|---|---|---|---|
| Used by AppGate to configure the client |
| String | yes | yes |
Examples
iOS using AirWatch MDM
Use the Workspace One UEM Admin Interface to add a key-value pair:
Key:
ag_configType:
StringValue:
"{"ag_url": "appgate://mycontroller.com/eyJW.....","mdm_approved": "SNdYpXJMOqnd0bIE"}"
iOS using Jamf Pro
The syntax required to deploy the client using Jamf Pro device management:
<dict>
<key>ag_config</key>
<string>{ "ag_url":"appgate://sdp-controllers.domain.com" }</string>
</dict>iOS using Safari for external authentication
Enter the following to enable Safari for external authentication:
"ag_use_safari_for_external_authentication": "true"
ChromeOS using Google
The syntax required to deploy the client using Google device management:
{
"applications": [{
"packageName": "com.cryptzone.appgate.xdp",
"installType": "FORCE_INSTALLED",
"defaultPermissionPolicy": "GRANT",
"managedConfiguration": {
"ag_config": "{ \"ag_url\": \"appgate:\/\/mycontroller.com\/eyJz.....GUifQ==\", \"Claim_ManagedDevice\": \"true\"}"
}
}]
}NOTE
The configuration is essentially the same as above—it uses additional delimiters in this case.
Android using MS Intune
The syntax required to deploy the client using MS Intune device management:
{
"kind": "androidenterprise#managedConfiguration",
"productId": "app:com.cryptzone.appgate.xdp",
"managedProperty": [
{
"key": "ag_config",
"valueString": "{\"ag_url\" : \"appgate://appgate.company.com/xxxx\", \"mdm_approved\": \"random key\"}"
}
]
}Checking for managed devices
One reason to include extra device claims is to let enterprises verify that a device is MDM-enabled before it can connect through AppGate ZTNA. Verifying this at run time is not possible because the security model of mobile operating systems prevents device claims from being collected using device scripts.
AppGate ZTNA must be installed through the MDM. At that point, the MDM populates the additional claims. These values are fixed and can include information the MDM can read that AppGate ZTNA cannot—such as an International Mobile Equipment Identity (IMEI) number. They can also be static claims such as mdm_version:1234 or mdm_managed:true. When the client connects, it sends these claims, and you can use them in policy assignment decisions. They are also recorded in the logs for audit purposes.
It may also be possible to include these claim values in external API calls. This lets you check a serial number against a database to verify the device before the policy is assigned.
Logs
Download logs from within the client using About > Download log files.
Removing settings
On iOS and iPadOS, you can wipe all settings, including the certificate saved when the client first connected.
In Settings, find AppGate ZTNA Settings and enable Wipe credentials on next launch.
.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A29%3A36Z&se=2026-11-21T21%3A42%3A36Z&sr=b&sp=r&sig=8muPZKCHuFilcJ8lJ5lFpJQpHbfV9Yvwbehs7L2aRuQ%3D)