Skip to content

Commit 8bcf6dc

Browse files
authored
ROPC not supported in hybrid identity scenarios
Addresses https://github.com/MicrosoftDocs/azure-docs/issues/32264
1 parent ca386b4 commit 8bcf6dc

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/active-directory/develop/v2-oauth-ropc.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.workload: identity
1313
ms.tgt_pltfrm: na
1414
ms.devlang: na
1515
ms.topic: conceptual
16-
ms.date: 08/30/2019
16+
ms.date: 09/17/2019
1717
ms.author: ryanwi
1818
ms.reviewer: hirsin
1919
ms.custom: aaddev
@@ -30,6 +30,7 @@ Microsoft identity platform supports the [resource owner password credential (RO
3030
> * Personal accounts that are invited to an Azure AD tenant can't use ROPC.
3131
> * Accounts that don't have passwords can't sign in through ROPC. For this scenario, we recommend that you use a different flow for your app instead.
3232
> * If users need to use multi-factor authentication (MFA) to log in to the application, they will be blocked instead.
33+
> * ROPC is not supported in hybrid identity scenarios (for example, Azure AD and ADFS used to authenticate on-premise accounts). If users are full-page redirected to an on-premises identity providers, Azure AD is not able to test the username and password against that identity provider.
3334
3435
## Protocol diagram
3536

0 commit comments

Comments
 (0)