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: articles/active-directory-b2c/secure-rest-api.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: kengaderdus
6
6
manager: CelesteDG
7
7
ms.service: azure-active-directory
8
8
ms.topic: how-to
9
-
ms.date: 01/11/2024
9
+
ms.date: 10/14/2024
10
10
ms.author: kengaderdus
11
11
ms.subservice: b2c
12
12
zone_pivot_groups: b2c-policy-type
@@ -276,7 +276,10 @@ A claim provides temporary storage of data during an Azure AD B2C policy executi
276
276
277
277
### Acquiring an access token
278
278
279
-
You can obtain an access token in one of several ways, for the [from a federated identity provider](idp-pass-through-user-flow.md), by calling a REST API that returns an access token, by using an [ROPC flow](../active-directory/develop/v2-oauth-ropc.md), or by using the [client credentials flow](../active-directory/develop/v2-oauth2-client-creds-grant-flow.md). The client credentials flow is commonly used for server-to-server interactions that must run in the background, without immediate interaction with a user.
279
+
You can obtain an access token in one of several ways, for the [from a federated identity provider](idp-pass-through-user-flow.md), by calling a REST API that returns an access token, by using an [ROPC flow](/entra/identity-platform/v2-oauth-ropc), or by using the [client credentials flow](../active-directory/develop/v2-oauth2-client-creds-grant-flow.md). The client credentials flow is commonly used for server-to-server interactions that must run in the background, without immediate interaction with a user.
280
+
281
+
> [!WARNING]
282
+
> Microsoft recommends you do *not* use the ROPC flow. This flow requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows aren't viable.
280
283
281
284
<aname='acquiring-an-azure-ad-access-token-'></a>
282
285
@@ -577,12 +580,12 @@ The following XML snippet is an example of a RESTful technical profile configure
577
580
```
578
581
::: zone-end
579
582
580
-
## Next steps
583
+
## Related content
581
584
582
585
::: zone pivot="b2c-user-flow"
583
586
- Get started with our [samples](api-connector-samples.md#api-connector-rest-api-samples).
584
587
::: zone-end
585
588
586
589
::: zone pivot="b2c-custom-policy"
587
590
- Learn more about the [Restful technical profile](restful-technical-profile.md) element in the custom policy reference.
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-how-to-premium-persistence.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -355,7 +355,9 @@ After a rewrite, two sets of AOF files exist in storage. Rewrites occur in the b
355
355
356
356
### Will having firewall exceptions on the storage account affect persistence?
357
357
358
-
Using managed identity adds the cache instance to the [trusted services list](../storage/common/storage-network-security.md?tabs=azure-portal), making firewall exceptions easier to carry out. If you aren't using managed identity and instead authorizing to a storage account using a key, then having firewall exceptions on the storage account tends to break the persistence process. This only applies to persistence in the Premium tier.
358
+
Yes. Using [firewall settings on the storage account](../storage/common/storage-network-security.md) can prevent the persistence feature from working. You can see if there are errors in persisting data by viewing the [Errors metric](monitor-cache-reference.md#azure-cache-for-redis-metrics). This metric will indicate if the cache is unable to persist data due to firewall restrictions on the storage account or other problems.
359
+
360
+
In order to use data persistence with a storage account that has a firewall set up, use [managed identity based authentication](cache-managed-identity.md) to connect to storage. Using managed identity adds the cache instance to the [trusted services list](../storage/common/storage-network-security.md?tabs=azure-portal), making firewall exceptions easier to carry out. If you aren't using managed identity and instead authorizing to a storage account using a key, then having firewall exceptions on the storage account tends to break the persistence process. This only applies to persistence in the Premium tier.
359
361
360
362
### Can I have AOF persistence enabled if I have more than one replica?
0 commit comments