-
Notifications
You must be signed in to change notification settings - Fork 21.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Error: AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret'. #61446
Comments
@ksaye Thanks for the feedback! We are currently investigating and will update you shortly. |
Hello @ksaye Thanks for reaching out to us!
|
Hello @ksaye I am able to repro the issue, Reason: I am not using the right Authentication Platform for my AAD application. Troubleshooting: |
@ksaye Does that answer your question? Do let us know if you are still blocked. |
@AshokPeddakotla-MSFT Thanks, that did fix it. I think the following document need to be changed: https://docs.microsoft.com/en-us/azure/digital-twins/how-to-set-up-instance-portal, as it instructs to use the web authentication no the mobile / desktop. |
Post migration from Angular 7 to 11 MSAL Log: [Tue, 27 Apr 2021 12:23:51 GMT] : : @azure/msal-browser@2.14.1 : Info - Emitting event: msal:handleRedirectStart BrowserConsoleAppender.append @ main-es2015.f147e7f539e3d0f3fc6a.js:1 |
Having the same issue here AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret'. |
using the ms-identity-javascript-react-spa example from documentation |
same for me, it doesn't work and asks for client_secret. |
@elenalash what do you mean when you say you moved it to an app? What kind of app did you move it to? |
I fixed mine when moved from redirect uri to SPA.
https://docs.microsoft.com/en-us/azure/active-directory/develop/migrate-spa-implicit-to-auth-code
Switch redirect URIs to SPA platform
If you'd like to continue using your existing app registration for your
applications, use the Azure portal to update the registration's redirect
URIs to the SPA platform. Doing so enables the authorization code flow with
PKCE and CORS support for apps that use the registration (you still need to
update your application's code to MSAL.js v2.x).
Follow these steps for app registrations that are currently configured with
Web platform redirect URIs:
1.
Sign in to the Azure portal <https://portal.azure.com/> and select
your Azure
Active Directory tenant.
2.
In App registrations, select your application, and then Authentication.
3.
In the Web platform tile under Redirect URIs, select the warning banner
indicating that you should migrate your URIs.
…On Fri, Jul 16, 2021 at 9:26 PM Dan Hellem ***@***.***> wrote:
@elenalash <https://github.com/elenalash> what do you mean when you say
you moved it to an app? What kind of app did you move it to?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#61446 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUPI4M56T4MDMTMRBCL2ECDTYBJDPANCNFSM4QJ3GH7A>
.
--
Regards,
Deepak
|
My code now throws a new error after changing from Web to SPA: invalid_request The below previously accepted answer of switch the platform to Mobile and desktop applications did the trick for me.
|
When running this sample code, specifically the last line:
I get the following error message.
It would appear that we need something where we create and send client_secret, something like: https://github.com/Azure/azure-sdk-for-net/blob/Azure.DigitalTwins.Core_1.0.0-preview.3/sdk/digitaltwins/Azure.DigitalTwins.Core/samples/DigitalTwinsClientSample/Program.cs#L65
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: