Skip to content

Commit f18660e

Browse files
Update pages that linked saying will soon be deprecated
1 parent 04789b9 commit f18660e

File tree

3 files changed

+4
-14
lines changed
  • src/content/docs

3 files changed

+4
-14
lines changed

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/renew-certificates.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,9 +13,7 @@ import { Render } from "~/components"
1313

1414
The exact method for certificate renewal depends on whether that hostname is proxying traffic through Cloudflare and whether it is a wildcard certificate.
1515

16-
Custom hostnames with DigiCert certificates currently have a validity period of one year, though DigiCert is [going to be deprecated](/ssl/reference/migration-guides/digicert-update/) soon as an option. Custom hostnames using Let's Encrypt, Google Trust Services, or SSL.com have a 90-day validity period.
17-
18-
Certificates are available for renewal 30 days before their expiration.
16+
Custom hostnames certificates have a 90-day validity period and are available for renewal 30 days before their expiration.
1917

2018
## Non-wildcard hostnames
2119

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/txt.mdx

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -62,12 +62,4 @@ You will then need to share these TXT tokens with your customers.
6262

6363
Your DCV tokens expire after a [certain amount of time](/cloudflare-for-platforms/cloudflare-for-saas/reference/token-validity-periods/), depending on your certificate authority.
6464

65-
This means that, if your customers take too long to place their tokens at their authoritative DNS provider, you may need to [get new tokens](#1-get-txt-tokens) and re-share them with your customer.
66-
67-
---
68-
69-
### DigiCert
70-
71-
If you create a hostname with DigiCert as the certificate authority, you only need to share one TXT record for your customer to place at their authoritative DNS provider.
72-
73-
However, Cloudflare [will soon be deprecating](/ssl/reference/migration-guides/digicert-update/) DigiCert as an issuing CA for custom hostnames, so we recommend you follow our [migration guide](/ssl/reference/migration-guides/digicert-update/custom-hostname-certificates/) to move your custom hostnames over to another CA.
65+
This means that, if your customers take too long to place their tokens at their authoritative DNS provider, you may need to [get new tokens](#1-get-txt-tokens) and re-share them with your customer.

src/content/docs/ssl/edge-certificates/troubleshooting/ca-faq.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,9 @@ Yes. Cloudflare can issue both RSA and ECDSA certificates.
2121

2222
### Which certificate authorities does Cloudflare use?
2323

24-
Cloudflare uses Let's Encrypt, Google Trust Services, SSL.com, Sectigo, and DigiCert. You can see a complete list of products and available CAs and algorithms in the [certificate authorities reference page](/ssl/reference/certificate-authorities/).
24+
Cloudflare uses Let's Encrypt, Google Trust Services, SSL.com, and Sectigo. You can see a complete list of products and available CAs and algorithms in the [certificate authorities reference page](/ssl/reference/certificate-authorities/).
2525

26-
[DigiCert will soon be removed as a CA from the Cloudflare pipeline](/ssl/reference/migration-guides/digicert-update/) and Sectigo is only used for [backup certificates](/ssl/edge-certificates/backup-certificates/).
26+
Sectigo is only used for [backup certificates](/ssl/edge-certificates/backup-certificates/).
2727

2828
### Are there any CA limitations I should know about?
2929

0 commit comments

Comments
 (0)