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/user-side-certificates/index.mdx
+26-1Lines changed: 26 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,7 +59,7 @@ Each Zero Trust account can generate a new root certificate a maximum of three t
59
59
## Activate a root certificate
60
60
61
61
:::note
62
-
Zero Trust accounts using the Cloudflare certificate prior to 2024-10-17 will need to redeploy and activate the newly generated certificate. Zero Trust accounts created during or after 2024-10-17 will use an available certificate by default.
62
+
Zero Trust accounts using the default Cloudflare certificate prior to 2024-10-17 will need to redeploy and activate the newly generated certificate. Zero Trust accounts created during or after 2024-10-17 will use an available certificate by default.
63
63
:::
64
64
65
65
Once a certificate is generated in or uploaded to Zero Trust, you need to activate it. Activating a certificate deploys it across the Cloudflare network. You can have up to 25 available certificates at once.
@@ -91,9 +91,34 @@ The status of the certificate will change to **Pending** while it deploys. Once
91
91
92
92
Once you deploy and install your certificate, you can turn it on for use in inspection:
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **Resources**.
95
97
2. In **Certificates**, select **Manage**.
96
98
3. Select the certificate you want to turn on.
97
99
4. In **Basic information**, select **Confirm and turn on certificate**.
98
100
101
+
</TabItem>
102
+
103
+
<TabItemlabel="API">
104
+
105
+
Send a `PUT` request to the [Update Zero Trust account configuration](/api/resources/zero_trust/subresources/gateway/subresources/configurations/methods/update/) endpoint. For example:
You can set multiple certificates to **Available**, but you can only turn on one certificate for use in inspection at a time. Setting a certificate as **In-Use** will set any other turned on certificates as **Available** and prevent them from being used for inspection until turned on again.
0 commit comments