diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/index.mdx index 7e496248803fc1..6aa2d2fbd9814b 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/index.mdx @@ -3,11 +3,13 @@ pcx_content_type: overview title: Custom hostnames sidebar: order: 3 - + label: About --- -import { DirectoryListing } from "~/components" +import { DirectoryListing } from "~/components"; Cloudflare for SaaS allows you, as a SaaS provider, to extend the benefits of Cloudflare products to custom domains by adding them to your zone as custom hostnames. We support adding hostnames that are a subdomain of your zone (for example, `sub.serviceprovider.com`) and vanity domains (for example, `customer.com`) to your SaaS zone. +## Resources + diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/index.mdx index 70a497f3df9448..99c74973725109 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/index.mdx @@ -3,12 +3,13 @@ title: Reference pcx_content_type: navigation sidebar: order: 11 + group: + hideIndex: true head: - tag: title content: Reference — Cloudflare for SaaS - --- -import { DirectoryListing } from "~/components" +import { DirectoryListing } from "~/components"; diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/index.mdx index bc647ee35545ef..6ebe9b579e933f 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/index.mdx @@ -3,10 +3,12 @@ pcx_content_type: navigation title: Status codes sidebar: order: 4 + group: + hideIndex: true --- +import { DirectoryListing } from "~/components"; + Cloudflare uses many different status codes for Cloudflare for SaaS. They can be related to: -- [Custom hostnames](/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-hostnames/) -- [Specific certificate authorities](/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/certificate-authority-specific/) -- [Custom Certificate Signing Requests](/cloudflare-for-platforms/cloudflare-for-saas/reference/status-codes/custom-csrs/) + diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/index.mdx index 566bf23f9f8b8f..80fd673837d7f4 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/saas-customers/provider-guides/index.mdx @@ -3,11 +3,12 @@ pcx_content_type: navigation title: Provider guides sidebar: order: 2 + group: + hideIndex: true head: [] description: Learn how to configure your Enterprise zone on several SaaS providers. - --- -import { DirectoryListing } from "~/components" +import { DirectoryListing } from "~/components"; diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/index.mdx index ee1d832ba09791..5387f322963cff 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/index.mdx @@ -1,13 +1,15 @@ --- pcx_content_type: overview -title: Certificate Management +title: Certificate management sidebar: order: 1 - + label: About --- -import { DirectoryListing } from "~/components" +import { DirectoryListing } from "~/components"; + +Cloudflare for SaaS takes away the burden of certificate issuance and management from you, as the SaaS provider, by proxying traffic through Cloudflare's edge. You can choose between Cloudflare managing all the certificate issuance and renewals on your behalf, or maintain control over your TLS private keys by uploading your customers' own certificates. -Cloudflare for SaaS takes away the burden of certificate issuance and management from the you, as the SaaS provider, by proxying traffic through Cloudflare's edge. You can choose between Cloudflare managing all the certificate issuance and renewals on your behalf, or maintain control over your TLS private keys by uploading your customers' own certificates. +## Resources diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/index.mdx index 62e8930f4b44a8..d12a94fa0c1063 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/index.mdx @@ -3,10 +3,11 @@ pcx_content_type: navigation title: Issue and validate certificates sidebar: order: 3 - + group: + hideIndex: true --- -import { DirectoryListing } from "~/components" +import { DirectoryListing } from "~/components"; Once you have [set up your Cloudflare for SaaS application](/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/), you can start issuing and validating certificates for your customers. diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx index e2f582195e4215..620511e3344b3b 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx @@ -3,14 +3,14 @@ pcx_content_type: overview title: WAF for SaaS sidebar: order: 1 - + label: Setup --- [Web Application Firewall (WAF)](/waf/) allows you to create additional security measures through Cloudflare. As a SaaS provider, you can link custom rules, rate limiting rules, and managed rules to your custom hostnames. This provides more control to keep your domains safe from malicious traffic. As a SaaS provider, you may want to apply different security measures to different custom hostnames. With WAF for SaaS, you can create multiple WAF configuration that you can apply to different sets of custom hostnames. This added flexibility and security leads to optimal protection across the domains of your end customers. -*** +--- ## Prerequisites @@ -46,10 +46,8 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \ :::note - One instance of low, medium, and high rules could be rate limiting. You can specify three different thresholds: low - 100 requests/minute, medium - 85 requests/minute, high - 50 requests/minute, for example. Another possibility is a WAF custom rule in which low challenges requests and high blocks them. - ::: 5. Make an API call in the format below using your Cloudflare email and the IDs gathered above: diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/index.mdx index f1c17d400ef673..585d6d58815fc0 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/index.mdx @@ -3,10 +3,10 @@ pcx_content_type: concept title: Apex proxying sidebar: order: 1 - + label: About --- -import { Render } from "~/components" +import { Render } from "~/components"; Apex proxying allows your customers to use their apex domains (`example.com`) with your SaaS application. @@ -24,4 +24,4 @@ This limitation does not apply with apex proxying. Cloudflare assigns a set of I ## Setup -* [Set up Apex Proxying](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/setup/) +- [Set up Apex Proxying](/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/apex-proxying/setup/) diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/index.mdx index baf96c6ed64c7a..a2bd4c493ff509 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/advanced-settings/index.mdx @@ -3,9 +3,10 @@ pcx_content_type: navigation title: Advanced Settings sidebar: order: 3 - + group: + hideIndex: true --- -import { DirectoryListing } from "~/components" +import { DirectoryListing } from "~/components"; diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/index.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/index.mdx index b047cc8061c9a7..f1e9f7631a3099 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/index.mdx +++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/start/index.mdx @@ -3,12 +3,13 @@ pcx_content_type: navigation title: Get started sidebar: order: 2 + group: + hideIndex: true head: - tag: title content: Get started - Cloudflare for SaaS - --- -import { DirectoryListing } from "~/components" +import { DirectoryListing } from "~/components";