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: content/cloudflare-one/connections/connect-devices/warp/user-side-certificates/custom-certificate.md
+36-4Lines changed: 36 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,15 +14,47 @@ Only available on Enterprise plans.
14
14
15
15
Enterprise customers who do not wish to install the [Cloudflare certificate](/cloudflare-one/connections/connect-devices/warp/user-side-certificates/install-cloudflare-cert/) have the option to upload their own root certificate to Cloudflare. Gateway will use your uploaded certificate to encrypt all sessions between the end user and Gateway, enabling all HTTPS inspection features that previously required the Cloudflare certificate. You can upload multiple certificates to your account, but only one can be active at any given time. You also need to upload a private key to intercept domains with JIT certificates and to enable the [block page](/cloudflare-one/policies/gateway/configuring-block-page/).
16
16
17
-
To generate a custom root CA, refer to [IBM's documentation](https://www.ibm.com/docs/en/runbook-automation?topic=certificate-generate-root-ca-key).
18
-
19
17
{{<Asidetype="warning">}}
20
18
Custom certificates are limited to use between your users and the Gateway proxy. Connections between Gateway and the origin server will use the Cloudflare certificate.
21
19
{{</Aside>}}
22
20
23
-
When preparing your certificate and private key for upload, be sure to remove any unwanted characters, such as mismatching subdomains in the certificate's common name.
21
+
## Generate a custom root CA
22
+
23
+
Before you generate a custom root CA, make sure you have [OpenSSL](https://www.openssl.org/) installed.
24
+
25
+
1. Open a terminal.
26
+
2. Create a directory for the root CA and change into it.
When preparing your certificate and private key for upload, be sure to remove any unwanted characters, such as mismatching subdomains in the certificate's common name. To review the private key, run the following command:
0 commit comments