You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Authentication**.
39
39
40
-
7. Name your identity provider and fill in the required fields with the information obtained in Step 3.
40
+
2. Under **Login methods**, select **Add new**.
41
41
42
-
8. (Optional) Enable [Proof of Key Exchange (PKCE)](https://www.oauth.com/oauth2-servers/pkce/) if the protocol is supported by your IdP. PKCE will be performed on all login attempts.
42
+
3. Choose **OpenID Connect**.
43
43
44
-
9. (Optional) To enable SCIM, refer to [Synchronize users and groups](#synchronize-users-and-groups).
44
+
4. Name your identity provider and fill in the required fields with the information obtained in Step 3.
45
45
46
-
10. (Optional) Under **Optional configurations**, enter [custom OIDC claims](#oidc-claims) that you wish to add to users' identity. This information will be available in the [user identity endpoint](/cloudflare-one/identity/authorization-cookie/application-token/#user-identity).
46
+
5. (Optional) Enable [Proof of Key Exchange (PKCE)](https://www.oauth.com/oauth2-servers/pkce/) if the protocol is supported by your IdP. PKCE will be performed on all login attempts.
47
47
48
-
11. Select **Save**.
48
+
6. (Optional) To enable SCIM, refer to [Synchronize users and groups](#synchronize-users-and-groups).
49
+
50
+
7. (Optional) Under **Optional configurations**, enter [custom OIDC claims](#oidc-claims) that you wish to add to users' identity. This information will be available in the [user identity endpoint](/cloudflare-one/identity/authorization-cookie/application-token/#user-identity).
51
+
52
+
8. Select **Save**.
53
+
54
+
</TabItem> <TabItemlabel="API">
55
+
56
+
1.[Create an API token](/fundamentals/api/get-started/create-token/) with the following permissions:
57
+
| Type | Item | Permission |
58
+
| ------- | ---------------- | ---------- |
59
+
| Account | Access: Organizations, Identity Providers, and Groups | Edit |
60
+
61
+
2. Make a `POST` request to the [Identity Providers](/api/resources/zero_trust/subresources/identity_providers/methods/create/) endpoint:
The following example requires Cloudflare provider version `>=4.40.0`.
87
+
:::
88
+
89
+
1. Add the following permission to your [`cloudflare_api_token`](https://registry.terraform.io/providers/cloudflare/cloudflare/4.40.0/docs/resources/api_token):
90
+
-`Access: Organizations, Identity Providers, and Groups Write`
91
+
92
+
2. Configure the [`cloudflare_zero_trust_access_identity_provider`](https://registry.terraform.io/providers/cloudflare/cloudflare/4.40.0/docs/resources/zero_trust_access_identity_provider) resource:
To test that your connection is working, go to **Authentication** > **Login methods** and select **Test** next to the login method you want to test. On success, a confirmation screen displays.
51
117
@@ -92,23 +158,6 @@ Cloudflare Access extends support for multi-record OIDC claims. These claims are
92
158
93
159
Cloudflare Access does not support partial OIDC claim value references or OIDC scopes.
Cloudflare Zero Trust integrates with any identity provider that supports SAML 2.0. If your identity provider is not listed in the integration list of login methods in Zero Trust, it can be configured using SAML 2.0 (or OpenID if OIDC based). Generic SAML can also be used if you would like to pass additional SAML headers or claims for an IdP in the integration list.
11
11
@@ -43,6 +43,9 @@ To download the SAML metadata file, copy-paste the metadata endpoint into a web
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Authentication** > **Login methods**.
47
50
2. Select **Add new** and select **SAML**.
48
51
3. Choose a descriptive name for your identity provider.
@@ -51,6 +54,34 @@ To download the SAML metadata file, copy-paste the metadata endpoint into a web
51
54
6. (Optional) Under **Optional configurations**, configure [additional SAML options](#optional-configurations).
52
55
7. Select **Save**.
53
56
57
+
</TabItem> <TabItemlabel="Terraform (v4)">
58
+
59
+
:::note[Provider versions]
60
+
The following example requires Cloudflare provider version `>=4.40.0`.
61
+
:::
62
+
63
+
1. Add the following permission to your [`cloudflare_api_token`](https://registry.terraform.io/providers/cloudflare/cloudflare/4.40.0/docs/resources/api_token):
64
+
-`Access: Organizations, Identity Providers, and Groups Write`
65
+
66
+
2. Configure the [`cloudflare_zero_trust_access_identity_provider`](https://registry.terraform.io/providers/cloudflare/cloudflare/4.40.0/docs/resources/zero_trust_access_identity_provider) resource:
You can now [test the IdP integration](/cloudflare-one/identity/idp-integration/#test-idps-in-zero-trust). A success response should return the configured SAML attributes.
Cloudflare Access can send a one-time PIN (OTP) to approved email addresses as an alternative to integrating an identity provider. You can simultaneously configure OTP login and the identity provider of your choice to allow users to select their own authentication method.
11
11
@@ -15,7 +15,35 @@ For example, if your team uses Okta but you are collaborating with someone outsi
1. In [Zero Trust](https://one.dash.cloudflare.com), go to **Settings** > **Authentication**.
21
+
2. Under **Login methods**, select **Add new**.
22
+
3. Select **One-time PIN**.
23
+
24
+
</TabItem> <TabItemlabel="Terraform (v4)">
25
+
26
+
:::note[Provider versions]
27
+
The following example requires Cloudflare provider version `>=4.40.0`.
28
+
:::
29
+
30
+
1. Add the following permission to your [`cloudflare_api_token`](https://registry.terraform.io/providers/cloudflare/cloudflare/4.40.0/docs/resources/api_token):
31
+
-`Access: Organizations, Identity Providers, and Groups Write`
32
+
33
+
2. Configure the [`cloudflare_zero_trust_access_identity_provider`](https://registry.terraform.io/providers/cloudflare/cloudflare/4.40.0/docs/resources/zero_trust_access_identity_provider) resource:
If your organization uses a third-party email scanning service (for example, Mimecast or Barracuda), add `[email protected]` to the email scanning allowlist.
46
+
:::
19
47
20
48
To grant a user access to an application, simply add their email address to an [Access policy](/cloudflare-one/policies/access/policy-management/#create-a-policy).
0 commit comments