[SSL] Update index.mdx #22103
[SSL] Update index.mdx #22103
Conversation
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryClarified the differences between Advanced Certificate Manager and Cloudflare for SaaS regarding cipher suites configuration.
Modified Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
|
Preview URL: https://a10098fe.preview.developers.cloudflare.com Files with changes (up to 15) |
| @@ -11,7 +11,8 @@ head: | |||
|
|
|||
| import { Render, TabItem, Tabs, DirectoryListing } from "~/components"; | |||
|
|
|||
| With an [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/) subscription, you can restrict connections between Cloudflare and clients — such as your visitor's browser — to specific [cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/). | |||
| With an [Advanced Certificate Manager](/ssl/edge-certificates/advanced-certificate-manager/) subscription, you can restrict connections between clients — such as your visitor's browser — and Cloudflare to specific [cipher suites](/ssl/edge-certificates/additional-options/cipher-suites/). | |||
| With a [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/) subscription, you can configure cipher suites for the connection between clients and [Custom Hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/). | |||
There was a problem hiding this comment.
Thank you for the PR, @ngayerie! I would like to suggest making it a blue box NOTE instead of a paragraph, since it's a guide for the Advanced Certificate subscription. This way, we can redirect people who start reading it and are looking for the Custom Hostname guide.
:::note
If you are a SaaS provider looking to restrict cipher suites for connections to [Custom Hostnames](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/), this can be configured with a [Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/) subscription. Refer to [TLS settings - Cloudflare for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/enforce-mtls/#cipher-suites) instead.
:::
And after that, we can delete the ### Cloudflare for SaaS part from this page entirely, as it caused confusion in the first place.
Summary
Clarifying ACM vs SaaS for the cipher suites configuration