Skip to content

Commit 7ba0044

Browse files
committed
refine context
1 parent 8ddf7f5 commit 7ba0044

File tree

1 file changed

+14
-6
lines changed

1 file changed

+14
-6
lines changed

src/content/docs/cloudflare-one/tutorials/warp-on-headless-linux.mdx

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,33 +8,37 @@ title: Deploy WARP on headless Linux machines
88

99
import { Render, GlossaryTooltip } from "~/components";
1010

11-
This tutorial explains how to deploy the Cloudflare WARP client on Linux devices using a service token and an installation script. This deployment workflow is designed for headless servers which do not have access to a browser for identity provider logins. Because users are not required to log in to an identity provider, identity-based policies and logging will not be available on these devices.
11+
This tutorial explains how to deploy the Cloudflare WARP client on Linux devices using a service token and an installation script. This deployment workflow is designed for headless servers - that is, servers which do not have access to a browser for identity provider logins - and for situations where you want to fully automate the onboarding process. Because devices will not register through an identity provider, [identity-based policies](/cloudflare-one/policies/gateway/identity-selectors/) and logging will be unavailable.
1212

1313
## Prerequisites
1414

1515
- [Cloudflare Zero Trust account](/cloudflare-one/setup/#create-a-zero-trust-organization)
1616

1717
## 1. Create a service token
1818

19-
A service token consists of a Client ID and a Client Secret. We will be using a service token to enroll the WARP client in your Zero Trust organization.
19+
Fully automated deployments rely on a service token to enroll the WARP client in your Zero Trust organization. You can use the same token to enroll multiple devices, or generate a unique token per device if they require different [device profile settings](/cloudflare-one/connections/connect-devices/warp/configure-warp/device-profiles/).
2020

21-
To create a new service token:
21+
To create a service token:
2222

2323
<Render file="access/create-service-token" product="cloudflare-one" />
2424

2525
## 2. Configure device enrollment permissions
2626

27+
Device enrollment permissions determine the users and devices that can register WARP with your Zero Trust organization.
28+
29+
To allow devices to enroll using a service token:
30+
2731
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **WARP Client**.
2832
2. In **Device enrollment permissions**, select **Manage**.
2933
3. In the **Policies** tab, select **Create new policy**. A new tab will open with the policy creation page.
3034
4. For **Action**, select _Service Auth_.
31-
5. For the **Selector** field, you have two options: you can either allow all service tokens (`Any Access Service Token`) or specific service tokens (`Service Token`). In this example, we will choose the token created earlier:
35+
5. For the **Selector** field, you have two options: you can either allow all service tokens (`Any Access Service Token`) or specific service tokens (`Service Token`). For example:
3236

3337
| Rule Action | Rule type | Selector | Value |
3438
| --------- | ---------| ------ | -- |
3539
| Service Auth | Include | Service Token | `<TOKEN-NAME>` |
3640
6. Save the policy.
37-
7. Go back to **Device enrollment permissions** and add the newly created policy.
41+
7. Go back to **Device enrollment permissions** and add the newly created policy to your permissions.
3842
8. Select **Save**.
3943

4044
## 3. Create an installation script
@@ -51,13 +55,15 @@ You can use a shell script to automate WARP installation and registration. The f
5155
#!/bin/bash
5256
set -e
5357

58+
# Download and install the WARP client
5459
function warp() {
5560
curl -fsSL https://pkg.cloudflareclient.com/pubkey.gpg | sudo gpg --yes --dearmor --output /usr/share/keyrings/cloudflare-warp-archive-keyring.gpg
5661
echo "deb [signed-by=/usr/share/keyrings/cloudflare-warp-archive-keyring.gpg] https://pkg.cloudflareclient.com/ $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/cloudflare-client.list
5762
sudo apt-get update --assume-yes
5863
sudo apt-get install --assume-yes cloudflare-warp
5964
}
6065

66+
# Create an MDM file with your WARP deployment parameters
6167
function mdm() {
6268
sudo touch /var/lib/cloudflare-warp/mdm.xml
6369
cat > /var/lib/cloudflare-warp/mdm.xml << "EOF"
@@ -94,6 +100,8 @@ You can use a shell script to automate WARP installation and registration. The f
94100
95101
## 4. Install WARP
96102
103+
To install WARP using the example script:
104+
97105
1. Make the script executable:
98106
99107
```sh
@@ -105,4 +113,4 @@ You can use a shell script to automate WARP installation and registration. The f
105113
sudo ./install_warp.sh
106114
```
107115
108-
The script will install WARP and apply the configuration parameters stored in `/var/lib/cloudflare-warp/mdm.xml`. Assuming [`auto_connect`](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/#auto_connect) is configured, WARP will automatically connect to your Zero Trust organization. The device will appear in [Zero Trust](https://one.dash.cloudflare.com) under **My Team** > **Devices**.
116+
WARP is now deployed with the configuration parameters stored in `/var/lib/cloudflare-warp/mdm.xml`. Assuming [`auto_connect`](/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/parameters/#auto_connect) is configured, WARP will automatically connect to your Zero Trust organization. Once connected, the device will appear in [Zero Trust](https://one.dash.cloudflare.com) under **My Team** > **Devices**.

0 commit comments

Comments
 (0)