You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/connections/connect-devices/warp/user-side-certificates/install-cert-with-warp.mdx
+23-20Lines changed: 23 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,14 +15,14 @@ import { Details } from "~/components";
<sup>*</sup> Only supported on Debian-based systems.
28
28
</Details>
@@ -41,18 +41,18 @@ The certificate is required if you want to [apply HTTP policies to encrypted web
41
41
42
42
If a custom certificate is not provided, WARP will install the default [Cloudflare certificate](/cloudflare-one/connections/connect-devices/warp/user-side-certificates/install-cloudflare-cert/#download-the-cloudflare-root-certificate) in the system keychain for all users. If you uploaded a custom certificate, the WARP client will deploy your custom certificate instead of the Cloudflare certificate.
43
43
44
-
Next, [verify](#view-the-installed-certificate) that the certificate was successfully installed.
44
+
Next, [verify](#access-the-installed-certificate) that the certificate was successfully installed.
45
45
46
46
:::note[Important]
47
-
48
47
WARP only installs the system certificate — it does not install the certificate on individual applications. You will need to [manually add the certificate](/cloudflare-one/connections/connect-devices/warp/user-side-certificates/install-cloudflare-cert/#add-the-certificate-to-applications) to applications that rely on their own certificate store.
49
-
50
48
:::
51
49
52
-
## View the installed certificate
50
+
## Access the installed certificate
53
51
54
52
### Windows
55
53
54
+
To access the installed certificate in Windows:
55
+
56
56
1. Open the Start menu and select **Run**.
57
57
2. Enter `certlm.msc`.
58
58
3. Go to **Trusted Root Certification Authority** > **Certificates**.
@@ -63,26 +63,29 @@ The certificate is also placed in `%ProgramData%\Cloudflare\installed_cert.pem`
63
63
64
64
### macOS
65
65
66
-
1. Open **Keychain Access**.
67
-
2. Go to **System** > **Certificates**.
68
-
3. Double-click your certificate. (The default Cloudflare certificate is named **Cloudflare for Teams ECC Certificate Authority**.)
69
-
4. You should see **This certificate is marked as trusted for all users**.
66
+
To access the installed certificate in Windows:
70
67
71
-
:::note
68
+
1. Open Keychain Access.
69
+
2. In **System Keychains**, go to **System** > **Certificates**.
70
+
3. Open your certificate. The default Cloudflare certificate is named **Cloudflare for Teams ECC Certificate Authority**.
71
+
4. If the certificate is trusted by all users, Keychain Access will display **This certificate is marked as trusted for all users**.
72
72
73
-
Certain macOS versions (`13.5` for example) do not allow WARP to automatically trust the certificate. To manually trust the certificate:
73
+
:::note
74
+
Certain macOS versions (such as macOS Ventura `13.5`) do not allow WARP to automatically trust the certificate. To manually trust the certificate:
74
75
75
76
1. Select **Trust**.
76
77
2. Set **When using this certificate** to _Always Trust_.
77
-
:::
78
+
79
+
Alternatively, you can configure your mobile device management (MDM) to automatically trust the certificate on all of your organization's devices.
80
+
:::
78
81
79
82
The certificate is also placed in `/Library/Application Support/Cloudflare/installed_cert.pem` for reference by scripts or tools.
80
83
81
84
### Linux
82
85
83
86
On Linux, the certificate is stored in `/usr/local/share/ca-certificates`. The default Cloudflare certificate is named `managed-warp.pem`.
84
87
85
-
If you do not see the certificate, run the following commands to update the system store:
88
+
If you cannot find the certificate, run the following commands to update the system store:
Cloudflare categorizes domains into content categories and security categories, which cover security risks and security threats:
7
6
8
-
***Content categories**: An upstream vendor supplies content categories for domains. These categories help us organize domains into broad topic areas. However, the specific criteria and methods used by our vendor may not be disclosed.
9
-
***Security risks**: Cloudflare determines security risks for domains using internal models. These models analyze various factors, including the age of a domain and its reputation. This allows us to identify potentially risky domains.
10
-
***Security threats**: To identify malicious domains that pose security threats, Cloudflare employs a mix of internal data sources, machine learning models, commercial feeds, and open-source threat intelligence.
7
+
-**Content categories**: An upstream vendor supplies content categories for domains. These categories help us organize domains into broad topic areas. However, the specific criteria and methods used by our vendor may not be disclosed.
8
+
-**Security risks**: Cloudflare determines security risks for domains using internal models. These models analyze various factors, including the age of a domain and its reputation. This allows us to identify potentially risky domains.
9
+
-**Security threats**: To identify malicious domains that pose security threats, Cloudflare employs a mix of internal data sources, machine learning models, commercial feeds, and open-source threat intelligence.
0 commit comments