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
If desktop, go to WARP page. If mobile, keep reading.
14
+
13
15
:::note
14
16
This procedure is only required to enable specific Cloudflare Zero Trust features, and should only be done at the direction of your IT department. This procedure is not required to enable the WARP client for consumers.
15
17
:::
@@ -18,7 +20,13 @@ If your device does not support [certificate installation via WARP](/cloudflare-
18
20
19
21
Zero Trust will only inspect traffic using installed certificates set to [**Available** and **In-Use**](/cloudflare-one/team-and-resources/devices/user-side-certificates/#activate-a-root-certificate).
20
22
21
-
## Download the Cloudflare root certificate
23
+
By following this guide, you will:
24
+
25
+
1. Download a Cloudflare certificate and verify it.
26
+
2. Install the certificate in your operating system's certificate store.
27
+
3. If a target application does not accept certificates from the operating system, you must install the certificate in the application's certificate store.
28
+
29
+
## 1. Download and verify the Cloudflare root certificate
22
30
23
31
:::note[Download limitation]
24
32
You can only download Cloudflare-generated certificates from the Zero Trust dashboard or with WARP.
Alternatively, you can download and install a certificate [using WARP](/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/#install-a-certificate-using-warp). WARP will add the certificates to the device's system certificate store in `installed_certs/<certificate_id>.pem`.
37
45
38
-
###Verify the downloaded certificate
46
+
##2. Verify the downloaded certificate
39
47
40
48
To verify your download, use a terminal to check that the downloaded certificate's hash matches the thumbprint listed under **Certificate thumbprint**. For example:
41
49
42
-
####SHA1
50
+
### SHA1
43
51
44
52
```sh title="SHA1 .crt example"
45
53
openssl x509 -noout -fingerprint -sha1 -inform der -in <certificate.crt>
Depending on your operating system, you may need to convert the certificate to a different file type.
79
89
80
90
Some applications require a certificate formatted in the `.cer` file type. You can convert your downloaded certificate using [OpenSSL](https://www.openssl.org/):
81
91
@@ -105,6 +115,10 @@ Some applications require a certificate formatted in the `.cer` file type. You c
105
115
106
116
## Add the certificate to operating systems
107
117
118
+
If you are deploying the Cloudflare certificate to desktop devices, use the [Install certificate using WARP](/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/) method.
119
+
120
+
Mobile devices require manual installations detailed in the instructions below.
121
+
108
122
### macOS
109
123
110
124
In macOS, you can choose the keychain in which you want to install the certificate. Each keychain impacts which users will be affected by trusting the root certificate.
@@ -298,14 +312,20 @@ After adding the Cloudflare certificate to ChromeOS, you may also have to [insta
298
312
299
313
## Add the certificate to applications
300
314
301
-
Some packages, development tools, and other applications provide options to trust root certificates that will allow for the traffic inspection features of Gateway to work without breaking the application.
315
+
Some applications do not use the system certificate store and therefore require the certificate to be added to the application directly. For certain applications like the ones below, you will need to follow the steps in this section and add the Cloudflare certificate to the application for TLS decryption to function properly.
316
+
317
+
If you do not update the application to trust the Cloudflare certificate, the application will refuse to connect and you will receive an untrusted certificate error.
302
318
303
-
All of the applications below first require downloading a Cloudflare certificate with the instructions above. On macOS, the default path to the system keychain database file is `/Library/Keychains/System.keychain`. On Windows, the default path is `\Cert:\CurrentUser\Root`.
319
+
All of the applications below first require downloading a Cloudflare certificate with [the instructions above](#download-the-cloudflare-root-certificate). On macOS, the default path to the system keychain database file is `/Library/Keychains/System.keychain`. On Windows, the default path is `\Cert:\CurrentUser\Root`.
304
320
305
321
:::note
306
322
Some applications require the use of a publicly trusted certificate — they do not trust the system certificate, nor do they have a configurable private store. For these applications to function, you must add a [Do Not Inspect policy](/cloudflare-one/traffic-policies/http-policies/#do-not-inspect) for the domains or IPs that the application relies on.
307
323
:::
308
324
325
+
:::caution
326
+
Even if you deployed WARP through the [Install certificate using WARP](/cloudflare-one/team-and-resources/devices/user-side-certificates/automated-deployment/) method, you may still need to add the Cloudflare certificate to certain applications. The Install certificate using WARP method only installs the Cloudflare certificate to the operating system certificate store.
0 commit comments