Skip to content

Commit efb16bf

Browse files
Enhance Cloudflare One Documentation Descriptions (#21799)
* Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Hyperlint Automation Fix * Update src/content/docs/cloudflare-one/applications/casb/troubleshooting/troubleshoot-integrations.mdx * Update src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/workday-saas.mdx * Update src/content/docs/cloudflare-one/index.mdx * Update src/content/docs/cloudflare-one/index.mdx * Update src/content/docs/cloudflare-one/index.mdx --------- Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> Co-authored-by: Kody Jackson <[email protected]>
1 parent 3257d15 commit efb16bf

File tree

5 files changed

+10
-9
lines changed

5 files changed

+10
-9
lines changed

src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/github-saas.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ This guide covers how to configure [GitHub Enterprise Cloud](https://docs.github
1919

2020
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
2121
2. Select **Add an application** > **SaaS** > **Select**.
22-
3. For **Application**, select *Github*.
22+
3. For **Application**, select *GitHub*.
2323
4. For the authentication protocol, select **SAML**.
2424
5. Select **Add application**.
2525
6. Fill in the following fields:
@@ -30,14 +30,14 @@ This guide covers how to configure [GitHub Enterprise Cloud](https://docs.github
3030
8. Configure [Access policies](/cloudflare-one/policies/access/) for the application.
3131
9. Save the application.
3232

33-
## 2. Create a x.509 certificate
33+
## 2. Create an X.509 certificate
3434

3535
1. Paste the **Public key** in a text editor.
3636
2. Wrap the certificate in `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`.
3737

3838
## 3. Configure an identity provider and SAML SSO in GitHub Enterprise Cloud
3939

40-
1. In your Github organization page, go to **Settings** > **Authentication security**.
40+
1. In your GitHub organization page, go to **Settings** > **Authentication security**.
4141
2. Under **SAML single sign-on**, turn on **Enable SAML authentication**.
4242
3. Fill in the following fields:
4343
* **Sign on URL**: SSO endpoint from application configuration in Cloudflare Zero Trust.

src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/pagerduty-saml-saas.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This guide covers how to configure [PagerDuty](https://support.pagerduty.com/doc
1818

1919
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
2020
2. Select **Add an application** > **SaaS**.
21-
3. For **Application**, select *Pagerduty*.
21+
3. For **Application**, select *PagerDuty*.
2222
4. For the authentication protocol, select **SAML**.
2323
5. Select **Add application**.
2424
6. Fill in the following fields:
@@ -32,7 +32,7 @@ This guide covers how to configure [PagerDuty](https://support.pagerduty.com/doc
3232
## 2. Create a x.509 certificate
3333

3434
1. Paste the **Public key** in a text editor.
35-
2. Amend the public key so each row is a maxiumum of 64 characters long. Originally, each full row of the public key is 65 characters long.
35+
2. Amend the public key so each row is a maximum of 64 characters long. Originally, each full row of the public key is 65 characters long.
3636
3. Wrap the certificate in `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`.
3737

3838
## 3. Add a SAML SSO provider to PagerDuty
@@ -45,7 +45,7 @@ This guide covers how to configure [PagerDuty](https://support.pagerduty.com/doc
4545

4646
## 4. Test the integration and finalize SSO configuration
4747

48-
1. Open an incognito window and paste your PagerDuty URL into the address bar. Select **Sign Ian With Single Sign-On**. You will be redirected to the Cloudflare Access login screen and prompted to sign in with your identity provider.
48+
1. Open an incognito window and paste your PagerDuty URL into the address bar. Select **Sign In With Single Sign-On**. You will be redirected to the Cloudflare Access login screen and prompted to sign in with your identity provider.
4949
2. In an incognito window, paste your PagerDuty URL and select **Sign In With Single Sign-On**. You will be redirected to the Cloudflare Access login screen and prompted to sign in with your identity provider.
5050
3. Once SSO sign in is successful, select your profile picture and go to **Account Settings** > **Single Sign-on**.
5151
4. Turn off **Allow username/password login** and select **Save Changes**. Now, users will only be able to sign in with SSO.

src/content/docs/cloudflare-one/applications/configure-apps/saas-apps/servicenow-saas-saml.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ This guide covers how to configure [ServiceNow](https://docs.servicenow.com/bund
4646
5. Paste the **SAML Metadata endpoint** from application configuration in Cloudflare Zero Trust in the empty field.
4747
6. Select **Import**.
4848
7. (Optional) Change the **Name** field to a more recognizable name.
49-
8. Turn off **sign AuthenRequest**.
49+
8. Turn off **Sign AuthnRequest**.
5050
9. Select **Update**.
5151
10. In the pop-up, select **Cancel** and then **>**.
5252
11. Select the **Name** of the configuration you just completed.

src/content/docs/cloudflare-one/index.mdx

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ sidebar:
77
head:
88
- tag: title
99
content: Overview
10+
description: Learn how to secure self-hosted and SaaS applications with Cloudflare Zero Trust. Configure a unified dashboard for seamless access and security.
1011
---
1112

1213
import { GlossaryTooltip, Render } from "~/components";
@@ -53,4 +54,4 @@ Cloudflare Zero Trust replaces legacy security perimeters with Cloudflare's glob
5354
## Availability
5455
Cloudflare Zero Trust offers both [Free and Paid plans](https://www.cloudflare.com/plans/zero-trust-services/). Access to certain features depends on a customer's plan type.
5556

56-
<Render file="non-contract-enablement" product="fundamentals" />
57+
<Render file="non-contract-enablement" product="fundamentals" />

src/content/docs/reference-architecture/design-guides/securing-guest-wireless-networks.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ Up to this point all methods mentioned have revolved around DNS, mainly due to t
172172
- Using IP address to reach sites (potentially saving IP to fully qualified domain name mappings via host file)
173173
- Using non sanctioned VPN clients
174174

175-
For these reasons you should also consider applying security in layers and add network centric enforcement to compliment the protections provided via DNS.
175+
For these reasons you should also consider applying security in layers and add network centric enforcement to complement the protections provided via DNS.
176176

177177
![Figure 4: This diagram shows how to connect guest networks to Cloudflare and the high level traffic flow to reach Internet resources.](~/assets/images/reference-architecture/securing-guest-wireless-networks/figure4.svg "Figure 4: This diagram shows how to connect guest networks to Cloudflare and the high level traffic flow to reach Internet resources.")
178178

0 commit comments

Comments
 (0)