Cloudflare One Agent managed configuration for Android
These are the managed configuration parameters Cloudflare documents for the Cloudflare One Agent on Android, which Cloudflare says replaced the legacy 1.1.1.1 app. They cover enrolling the device in your Zero Trust organization, how the client behaves and which apps go through it. Cloudflare publishes one parameter list for several platforms and marks platform limits on some of them, such as use_in_app_webview and unique_client_id, which are valid for Android. Check Cloudflare's page for the platform and client version of any other parameter before you rely on it.
Copy a setup into the managed configuration of a policy, then adjust the values. Each one uses only keys explained below.
Enrol with sign-in and keep it on
Register the device in your organization, skip the intro screens and stop people switching the client off. Cloudflare requires auto_connect with this lock on new deployments, so the client starts connected.
Sets how the client works, from full tunnelling to posture checks only. The proxy option also reads proxy_port.
warp
switch_locked
On or off
Stops people from turning the client off. Use it when protection must stay on at all times. On new deployments, also set auto_connect to 0 or higher, so the client does not start switched off with no way to turn it on.
true
auto_connect
Minutes, 0 to 1440
If someone switches the client off, it turns itself back on after this many minutes. Zero leaves it off until they turn it on.
15
gateway_unique_id
DNS location subdomain
Sends DNS queries to a specific Gateway DNS location so the right filtering policy applies.
abcd1234
support_url
https or mailto link
Turns the feedback button back on and points it to your own help page or mailbox.
mailto:it@example.com
unique_client_id
Device UUID
A unique identifier for the device that the UUID posture check in Zero Trust can match against. Android and ChromeOS only.
6f9619ff-8b86-d011-b42d-00cf4fc964ff
Per-app tunnel
app_identifier
Package name
Names an Android app whose traffic should go through the client. Add one entry for each app you want tunnelled.
com.example.erp
is_browser
On or off
Marks a per-app entry as a browser so the client can ask for re-authentication and show block notices there.
true
Deploy with Nomid
Roll Cloudflare One Agent out in three steps
Step 1Add Cloudflare One Agent to a policy
Find it on Google Play from the policy’s apps list and choose how it is installed.
Step 2Set its managed configuration
In the policy, set the app’s managed configuration with the keys and values from this page.
Step 3Assign the policy
Devices in the policy receive Cloudflare One Agent and its configuration on their next sync.
Questions
Cloudflare One Agent on managed Android
What is Cloudflare One Agent's package name on Android?
com.cloudflare.cloudflareoneagent. Cloudflare's download page links the legacy 1.1.1.1 app under com.cloudflare.onedotonedotonedotone and says the Cloudflare One Agent has replaced it.
What happened to the old 1.1.1.1 app?
Cloudflare's download page says the legacy Android client has been replaced by the Cloudflare One Agent and points to a migration guide. This page does not cover that guide.
Can the device enrol without a person signing in?
Yes, with auth_client_id and auth_client_secret from a service token. Keep in mind the secret is stored in your MDM policy.
Do all parameters on Cloudflare's page work on Android?
No. Some are for Windows or macOS only. Check Cloudflare's parameter page for the platform column before you rely on one.