Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -123,11 +123,11 @@ Intune allows you to insert [predefined variables](https://learn.microsoft.com/e
Per-app VPN is supported on Cloudflare One Agent version `1.8` or greater for iOS.
:::

Before proceeding with per-app VPN configuration, you must make sure Auto connect is disabled for your organization in the Cloudflare dashboard. To disable Auto connect:
Before proceeding with per-app VPN configuration, you must make sure [Auto connect](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#auto-connect) is disabled in Zero Trust. To disable Auto connect:

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
2. Select **Zero Trust** > **Settings** > **WARP Client**.
3. Go to **Device Settings** > select your profile and select **Edit** > toggle **Auto Connect** off.
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **WARP Client**.
2. Under **Device Settings**, select your device profile and select **Edit**.
3. Turn off **Auto Connect**.

To configure per-app VPN:

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -78,11 +78,11 @@ Jamf is now configured to deploy the Cloudflare One Agent.
Per-app VPN is supported on Cloudflare One Agent version `1.8` or greater for iOS.
:::

Before proceeding with per-app VPN configuration, you must make sure Auto connect is disabled for your organization in the Cloudflare dashboard. To disable Auto connect:
Before proceeding with per-app VPN configuration, you must make sure [Auto connect](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/#auto-connect) is disabled in Zero Trust. To disable Auto connect:

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
2. Select **Zero Trust** > **Settings** > **WARP Client**.
3. Go to **Device Settings** > select your profile and select **Edit** > toggle **Auto Connect** off.
1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Settings** > **WARP Client**.
2. Under **Device Settings**, select your device profile and select **Edit**.
3. Turn off **Auto Connect**.

To configure per-app VPN:

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ description: Review FAQs about getting started with Cloudflare Zero Trust.

## How do I sign up for Cloudflare Zero Trust?

You can sign up today at [this link](https://dash.cloudflare.com/sign-up/teams). Follow the onboarding steps, choose a team name and a payment plan, and start protecting your network in just a few minutes.
You can sign up today at [this link](https://one.dash.cloudflare.com). Follow the onboarding steps, choose a team name and a payment plan, and start protecting your network in just a few minutes.

## What is a team domain/team name?

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ sidebar:
order: 4
---

import { Render, PackageManagers } from "~/components";
import { Render, PackageManagers, DashButton } from "~/components";

Cross-Origin Resource Sharing ([CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)) is a mechanism that uses HTTP headers to grant a web application running on one origin permission to reach selected resources in a different origin. The web application executes a cross-origin HTTP request when it requests a resource that has a different origin from its own, including domain, protocol, or port.

Expand Down Expand Up @@ -220,7 +220,9 @@ npx wrangler deploy

### 4. Configure the Worker

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), select your account and go to **Workers & Pages**.
1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to the **Workers & Pages** page.

<DashButton url="/?to=/:account/workers-and-pages" />

2. Select your newly created Worker.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -148,7 +148,7 @@ The following example requires Cloudflare provider version `4.40.0` or greater.

If your organization's UPNs do not match users' email addresses, you must add a custom claim for email. For example, if your organization's email format is `[email protected]` but the UPN is `[email protected]`, you must create an email claim if you are configuring email-based policies.

By default, Cloudflare will first look for the unique claim name you created and configured in the Cloudflare dashboard to represent email (for example, `email_identifier`) in the `id_token` JSON response. If you did not configure a unique claim name, Cloudflare will then look for an `email` claim. Last, if neither claim exists, Cloudflare will look for the UPN claim.
By default, Cloudflare will first look for the unique claim name you created and configured in Zero Trust to represent email (for example, `email_identifier`) in the `id_token` JSON response. If you did not configure a unique claim name, Cloudflare will then look for an `email` claim. Last, if neither claim exists, Cloudflare will look for the UPN claim.

To receive an email claim in the `id_token` from Microsoft Entra, you must:

Expand All @@ -159,8 +159,11 @@ To receive an email claim in the `id_token` from Microsoft Entra, you must:

The example above includes both a UPN claim and an email claim. Because an email claim was created in the Microsoft Entra configuration, Cloudflare will look for the `email` key-value pair in the JSON response.

3. If you gave your email claim another name than `email`, you must update your configuration in the Cloudflare dashboard. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Authentication** > **Azure AD** > **Edit**.
4. Under **Optional configurations** > **Email claim**, enter the name of the claim representing your organization's email addresses.
3. If you gave your email claim another name than `email`, you must update your configuration in Zero Trust:

a. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Authentication** > **Azure AD** > **Edit**.

b. Under **Optional configurations** > **Email claim**, enter the name of the claim representing your organization's email addresses.

#### Object ID

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ To set up Keycloak (SAML) as your identity provider:

Next, you will need to integrate with Cloudflare Access.

8. In Zero Trust, go to **Settings** > **Authentication**.
8. In [Zero Trust](https://dash.cloudflare.com), go to **Settings** > **Authentication**.

9. Under **Login methods**, select **Add new**.

Expand Down
7 changes: 4 additions & 3 deletions src/content/docs/cloudflare-one/identity/service-tokens.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ sidebar:
order: 6
---

import { AvailableNotifications, Render, APIRequest } from "~/components";
import { AvailableNotifications, Render, APIRequest, DashButton } from "~/components";

You can provide automated systems with service tokens to authenticate against your Zero Trust policies. Cloudflare Access will generate service tokens that consist of a Client ID and a Client Secret. Automated systems or applications can then use these values to reach an application protected by Access.

Expand Down Expand Up @@ -123,11 +123,12 @@ An alert can be configured to notify a week before a service token expires to al

To configure a service token expiration alert:

1. In the [Cloudflare dashboard](https://dash.cloudflare.com), go to the **Notifications** tab.
1. In the [Cloudflare dashboard](https://dash.cloudflare.com), go to the **Notifications** page.
<DashButton url="/?to=/:account/notifications" />
2. Select **Add**.
3. Select _Expiring Access Service Token_.
4. Enter a name for your alert and an optional description.
5. (Optional) Add other recipients for the notification email.
6. Select **Save**.

Your alert has been set and is now visible in the **Notifications** tab of the Cloudflare dashboard.
Your alert has been set and is now visible on the **Notifications** page.
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ tags:
- JavaScript
---

import { TypeScriptExample } from "~/components";
import { TypeScriptExample, DashButton } from "~/components";

This tutorial covers how to use a [Cloudflare Worker](/workers/) to add custom HTTP headers to traffic, and how to send those custom headers to your origin services protected by [Cloudflare Access](/cloudflare-one/policies/access/).

Expand All @@ -25,7 +25,9 @@ Some applications and networking implementations require specific custom headers

## Before you begin

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. Go to **Workers & Pages**.
1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), go to the **Workers & Pages** page.

<DashButton url="/?to=/:account/workers-and-pages" />

2. If this is your first Worker, select **Create Worker**. Otherwise, select **Create application**, then select **Create Worker**.

Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/cloudflare-one/tutorials/kubectl.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,7 @@ ingress:

You can now create a DNS record that will route traffic to this Tunnel. Multiple DNS records can point to a single Tunnel and will send traffic to the configured service as long as the hostname is defined with an [ingress rule](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/configuration-file/#file-structure-for-public-hostnames).

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. Select your domain and go to **DNS**.
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account. Select your domain and go to **DNS** > **Records**.

2. Select **Add record**. Choose `CNAME` as the record type. For **Name**, choose the hostname where you want to create a Tunnel. This should match the hostname of the Access policy.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,8 @@ You only need to add one domain to Cloudflare, since you can create an infinite
## Add a site to Cloudflare

1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
2. Select **Add a site**.
3. Enter your websites apex domain (`example.com`).
2. Select **Onboard a domain**.
3. Enter your website's apex domain (`example.com`).
4. Select a [plan](https://www.cloudflare.com/plans/#compare-features) for this website. Everything you need to do with the domain in Cloudflare Zero Trust is available on the **Free** plan.
5. Select **Continue**. Cloudflare will scan your website for any configured DNS records.

Expand Down
6 changes: 4 additions & 2 deletions src/content/partials/cloudflare-one/choose-team-name.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,11 @@

---

import { GlossaryTooltip } from "~/components"
import { GlossaryTooltip, DashButton } from "~/components"

1. On your Account Home in the [Cloudflare dashboard](https://dash.cloudflare.com/), select the **Zero Trust** icon.
1. In the [Cloudflare dashboard](https://dash.cloudflare.com/), select **Zero Trust**.

<DashButton url="one.dash.cloudflare.com" />

2. On the onboarding screen, choose a <GlossaryTooltip term="team name">team name</GlossaryTooltip>. The team name is a unique, internal identifier for your Zero Trust organization. Users will enter this team name when they enroll their device manually, and it will be the subdomain for your App Launcher (as relevant). Your business name is the typical entry.

Expand Down