cloudflare · kodster28 · Apr 17, 2025 · Apr 17, 2025 · Apr 17, 2025 · Apr 17, 2025
@@ -19,7 +19,7 @@ This guide covers how to configure [GitHub Enterprise Cloud](https://docs.github
 
 1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
 2. Select **Add an application** > **SaaS** > **Select**.
-3. For **Application**, select *Github*.
+3. For **Application**, select *GitHub*.
 4. For the authentication protocol, select **SAML**.
 5. Select **Add application**.
 6. Fill in the following fields:
@@ -30,14 +30,14 @@ This guide covers how to configure [GitHub Enterprise Cloud](https://docs.github
 8. Configure [Access policies](/cloudflare-one/policies/access/) for the application.
 9. Save the application.
 
-## 2. Create a x.509 certificate
+## 2. Create an X.509 certificate
 
 1. Paste the **Public key** in a text editor.
 2. Wrap the certificate in `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`.
 
 ## 3. Configure an identity provider and SAML SSO in GitHub Enterprise Cloud
 
-1. In your Github organization page, go to **Settings** > **Authentication security**.
+1. In your GitHub organization page, go to **Settings** > **Authentication security**.
 2. Under **SAML single sign-on**, turn on **Enable SAML authentication**.
 3. Fill in the following fields:
    * **Sign on URL**:  SSO endpoint from application configuration in Cloudflare Zero Trust.

@@ -18,7 +18,7 @@ This guide covers how to configure [PagerDuty](https://support.pagerduty.com/doc
 
 1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Access** > **Applications**.
 2. Select **Add an application** > **SaaS**.
-3. For **Application**, select *Pagerduty*.
+3. For **Application**, select *PagerDuty*.
 4. For the authentication protocol, select **SAML**.
 5. Select **Add application**.
 6. Fill in the following fields:
@@ -32,7 +32,7 @@ This guide covers how to configure [PagerDuty](https://support.pagerduty.com/doc
 ## 2. Create a x.509 certificate
 
 1. Paste the **Public key** in a text editor.
-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.
+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.
 3. Wrap the certificate in `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----`.
 
 ## 3. Add a SAML SSO provider to PagerDuty
@@ -45,7 +45,7 @@ This guide covers how to configure [PagerDuty](https://support.pagerduty.com/doc
 
 ## 4. Test the integration and finalize SSO configuration
 
-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.
+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.
 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.
 3. Once SSO sign in is successful, select your profile picture and go to **Account Settings** > **Single Sign-on**.
 4. Turn off **Allow username/password login** and select **Save Changes**. Now, users will only be able to sign in with SSO.
@@ -46,7 +46,7 @@ This guide covers how to configure [ServiceNow](https://docs.servicenow.com/bund
 5. Paste the **SAML Metadata endpoint** from application configuration in Cloudflare Zero Trust in the empty field.
 6. Select **Import**.
 7. (Optional) Change the **Name** field to a more recognizable name.
-8. Turn off **sign AuthenRequest**.
+8. Turn off **Sign AuthnRequest**.
 9. Select **Update**.
 10. In the pop-up, select **Cancel** and then **>**.
 11. Select the **Name** of the configuration you just completed.

@@ -7,6 +7,8 @@ sidebar:
 head:
   - tag: title
     content: Overview
+  - tag: meta
+    description: 'Learn how to secure self-hosted and SaaS applications with Cloudflare Zero Trust. Configure a unified dashboard for seamless access and security.'
 ---
 
 import { GlossaryTooltip, Render } from "~/components";
@@ -53,4 +55,4 @@ Cloudflare Zero Trust replaces legacy security perimeters with Cloudflare's glob
 ## Availability
 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.
 
-<Render file="non-contract-enablement" product="fundamentals" />
+<Render file="non-contract-enablement" product="fundamentals" />
@@ -172,7 +172,7 @@ Up to this point all methods mentioned have revolved around DNS, mainly due to t
 - Using IP address to reach sites (potentially saving IP to fully qualified domain name mappings via host file)
 - Using non sanctioned VPN clients
 
-For these reasons you should also consider applying security in layers and add network centric enforcement to compliment the protections provided via DNS.
+For these reasons you should also consider applying security in layers and add network centric enforcement to complement the protections provided via DNS.
 
 ![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.")