Skip to content
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,8 @@ head:

---

import { APIRequest } from "~/components";

Refer to the following sections to learn how to manage certificates used with the different Authenticated Origin Pulls setups.

## Use specialized certificates
Expand All @@ -33,13 +35,29 @@ However, requests are dropped at your origin if your origin only accepts a valid

## Replace a client cert (without downtime)

For hostname:
### Per-hostname

1. [Upload the new certificate](/api/resources/origin_tls_client_auth/subresources/hostnames/subresources/certificates/methods/create/).

2. [Enable Authenticated Origin Pulls for that specific hostname](/api/resources/origin_tls_client_auth/subresources/hostnames/methods/update/).

For global:
2. [List your certificates](/api/resources/origin_tls_client_auth/subresources/hostnames/subresources/certificates/methods/list/) and note the ID for the certificate you uploaded.

3. [Enable Authenticated Origin Pulls for the specific hostname](/api/resources/origin_tls_client_auth/subresources/hostnames/methods/update/) and enable the certificate you want to be used with the ID obtained in step 2:

<APIRequest
path="/zones/{zone_id}/origin_tls_client_auth/hostnames"
method="PUT"
json={{
"config": [
{
"enabled": true,
"hostname": "<HOSTNAME>",
"cert_id": "<CERT_ID>"
}
]
}}
/>

### Zone-level

1. [Upload the new certificate](/api/resources/origin_tls_client_auth/methods/create/).

Expand Down
Loading