Skip to content

Commit 477a222

Browse files
Merge pull request #288310 from kengaderdus/remediate-add-ropc-policy
[SFI Remediate] ROPC flow
2 parents 4dd3196 + 8fd14cc commit 477a222

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

articles/active-directory-b2c/secure-rest-api.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: kengaderdus
66
manager: CelesteDG
77
ms.service: azure-active-directory
88
ms.topic: how-to
9-
ms.date: 01/11/2024
9+
ms.date: 10/14/2024
1010
ms.author: kengaderdus
1111
ms.subservice: b2c
1212
zone_pivot_groups: b2c-policy-type
@@ -276,7 +276,10 @@ A claim provides temporary storage of data during an Azure AD B2C policy executi
276276

277277
### Acquiring an access token
278278

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.
280283
281284
<a name='acquiring-an-azure-ad-access-token-'></a>
282285

@@ -577,12 +580,12 @@ The following XML snippet is an example of a RESTful technical profile configure
577580
```
578581
::: zone-end
579582

580-
## Next steps
583+
## Related content
581584

582585
::: zone pivot="b2c-user-flow"
583586
- Get started with our [samples](api-connector-samples.md#api-connector-rest-api-samples).
584587
::: zone-end
585588

586589
::: zone pivot="b2c-custom-policy"
587590
- Learn more about the [Restful technical profile](restful-technical-profile.md) element in the custom policy reference.
588-
::: zone-end
591+
::: zone-end

0 commit comments

Comments
 (0)