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
Copy file name to clipboardExpand all lines: src/content/docs/cloudflare-one/identity/idp-integration/entra-id.mdx
+43-36Lines changed: 43 additions & 36 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,12 @@ To retrieve those values:
53
53
54
54
12. Name the client secret and choose an expiration period.
55
55
56
+
:::note
57
+
58
+
When the client secret expires, users will be unable to log in through Access. Take note of your expiry date to prevent login errors and renew your client secret when necessary.
59
+
60
+
:::
61
+
56
62
13. After the client secret is created, copy its **Value** field. Store the client secret in a safe place, as it can only be viewed immediately after creation.
57
63
58
64

@@ -120,7 +126,7 @@ The Microsoft Entra ID integration allows you to synchronize IdP groups and auto
@@ -139,9 +145,9 @@ SCIM requires a separate enterprise application from the one created during [ini
139
145
140
146
5. Once the SCIM application is created, [assign users and groups to the application](https://learn.microsoft.com/entra/identity/enterprise-apps/assign-user-or-group-access-portal).
141
147
142
-
:::note
143
-
Groups in this SCIM application should match the groups in your other [Cloudflare Access enterprise application](/cloudflare-one/identity/idp-integration/entra-id/#set-up-entra-id-as-an-identity-provider). Because SCIM group membership updates will overwrite any groups in a user's identity, assigning the same groups to each app ensures consistent policy evaluation.
144
-
:::
148
+
:::note
149
+
Groups in this SCIM application should match the groups in your other [Cloudflare Access enterprise application](/cloudflare-one/identity/idp-integration/entra-id/#set-up-entra-id-as-an-identity-provider). Because SCIM group membership updates will overwrite any groups in a user's identity, assigning the same groups to each app ensures consistent policy evaluation.
150
+
:::
145
151
146
152
6. Go to **Provisioning** and select **Get started**.
147
153
@@ -159,7 +165,7 @@ SCIM requires a separate enterprise application from the one created during [ini
159
165
160
166
To check which users and groups were synchronized, select **View provisioning logs**.
161
167
162
-
<Renderfile="access/verify-scim-provisioning"/>
168
+
<Renderfile="access/verify-scim-provisioning"/>
163
169
164
170
### Provisioning attributes
165
171
@@ -207,38 +213,39 @@ Access and Gateway policies for an Entra group will also apply to all [nested gr
207
213
## Force user interaction during WARP reauthentication
208
214
209
215
You can require users to re-enter their credentials into Entra ID whenever they [re-authenticate their WARP session](/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-sessions/). To configure this setting:
216
+
210
217
1. Make a `GET` request to the [Identity Providers endpoint](/api/resources/zero_trust/subresources/identity_providers/) and copy the response for the Entra ID identity provider.
211
218
2.[Update the Entra ID identity provider](/api/resources/zero_trust/subresources/identity_providers/methods/update/) using a `PUT` request. In the request body, include all existing configurations and set the `prompt` parameter to either `login` or `select_account`. For example,
0 commit comments