Skip to content

Commit f453eb4

Browse files
[SSL] Cert replacement status and API Access requirement (#21917)
* Add dedicated section for cert replacement * Add API Access note to Origin CA setup page * Apply suggestions from code review Co-authored-by: Jun Lee <[email protected]> --------- Co-authored-by: Jun Lee <[email protected]>
1 parent 499e4aa commit f453eb4

File tree

2 files changed

+10
-1
lines changed

2 files changed

+10
-1
lines changed

src/content/docs/ssl/origin-configuration/origin-ca/index.mdx

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,6 +36,9 @@ To create an Origin CA certificate in the dashboard:
3636
2. Choose a domain.
3737
3. Go to **SSL/TLS** > **Origin Server**.
3838
4. Select **Create Certificate**.
39+
:::note[API Access required]
40+
Users who do not have [**API Access**](https://dash.cloudflare.com/?to=/:account/members) will receive an error while trying to perform this action. Refer to [Troubleshooting](/ssl/origin-configuration/origin-ca/troubleshooting/#this-zone-is-either-not-part-of-your-account-or-you-do-not-have-access-to-it) for guidance.
41+
:::
3942
5. Choose either:
4043
* **Generate private key and CSR with Cloudflare**: Private key type can be RSA or ECC.
4144
* **Use my private key and CSR**: Paste the Certificate Signing Request into the text field.

src/content/docs/ssl/reference/certificate-statuses.mdx

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ description: Understand certificate statuses in Cloudflare SSL/TLS, including st
99
Certificates statuses show which stage of the issuance process each certificate is in.
1010
## New certificates
1111

12-
When you order a new certificate, either an [edge certificate](/ssl/edge-certificates/) or a certificate used for a [custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/), its status will move through various stages as it progresses to Cloudflares global network:
12+
When you order a new certificate, either an [edge certificate](/ssl/edge-certificates/) or a certificate used for a [custom hostname](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/), its status will move through various stages as it progresses to Cloudflare's global network:
1313

1414
1. Initializing
1515
2. Pending Validation
@@ -21,6 +21,12 @@ Once you issue a certificate, it should be in **Pending Validation**, but change
2121

2222
If you deactivate a certificate, it will become a **Deactivating** and then an **Inactive** status.
2323

24+
### Certificate replacement
25+
26+
When replacing a certificate, you may note a **Pending Cleanup** status. Old certificates are not deleted until the replacement has been successfully issued. This ensures TLS will not break for the hostname while the certificate is being replaced.
27+
28+
When the new certificate is successfully issued and activated, the status for the old certificate will transition from **Pending Cleanup**, and the certificate will be deleted.
29+
2430
## Custom certificates
2531

2632
If you are using a [custom certificate](/ssl/edge-certificates/custom-certificates/) and your [zone status](/dns/zone-setups/reference/domain-status/) is **Pending** or **Moved**, your certificate may have a status of **Holding Deployment**.

0 commit comments

Comments
 (0)