Skip to content

Commit ec42a45

Browse files
authored
add images
1 parent 85d93bc commit ec42a45

2 files changed

Lines changed: 5 additions & 3 deletions

File tree

support/entra/entra-id/app-integration/confidential-client-application-authentication-error-aadsts7000218.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,11 +32,13 @@ This issue occurs because the application doesn't provide its credential (a clie
3232

3333
To resolve this issue, include the client secret or client assertion in the token request.
3434

35-
In some authentication flow scenarios such as [OAuth 2 Resource Owner Password Credentials (ROPC)](/entra/identity-platform/v2-oauth-ropc) grant flow or [OAuth 2 device authorization grant flow](/entra/identity-platform/v2-oauth2-device-code) where you don't expect the client application to be confidential, change the default client type to public in the **App registrations**:
35+
In some authentication flow scenarios such as [OAuth 2 Resource Owner Password Credentials (ROPC)](/entra/identity-platform/v2-oauth-ropc) grant flow or [OAuth 2 device authorization grant flow](/entra/identity-platform/v2-oauth2-device-code) where you don't expect the client application to be confidential, allow public client flows in the **App registrations**:
3636

3737
1. In the [Azure portal](https://portal.azure.com/), in **App registrations**, select your application, and then select **Authentication**.
38-
2. Select **Advanced settings** > **Default client type**.
39-
3. For **Treat application as a public client**, select **Yes**.
38+
2. Select **Advanced settings** > **Allow public client flows**.
39+
3. For **Enable the following mobile and desktop flows**, select **Yes**.
40+
41+
:::image type="content" source="media/confidential-client-application-authentication-error-aadsts7000218/allow-public-client-flows.png" alt-text="Screenshot that shows the 'Enable the following mobile and desktop flows' option" lightbox="media/confidential-client-application-authentication-error-aadsts7000218/allow-public-client-flows.png":::
4042

4143
Changing the default client type from confidential to public causes security implications. For more information, see [What’s the security implication of changing the default client type from confidential to public in Azure AD?](https://blogs.aaddevsup.xyz/2020/09/whats-the-security-implication-of-changing-the-default-client-type-from-confidential-to-public-in-azure-ad/)
4244

Loading

0 commit comments

Comments
 (0)