Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Dynamics Integration Auth Failure

  • 1.  Dynamics Integration Auth Failure

    Posted 06-05-2025 18:48

    Adrian_Santamaria | 2019-09-03 07:56:40 UTC | #1

    Hello

    I'm trying to use the MS Dynamics integration, but every time I execute a Data Action test, it returns this error:

    { "status": 400, "code": "invalid.credentials", "entityName": "msDynamics", "message": "There was an issue validating the credentials.", "messageParams": {}, "contextId": "0e764ac0-47f5-4494-b393-bfa3822248c7", "details": [ { "errorCode": "ACTION.AUTHENTICATION" } ], "errors": [ { "status": 401, "code": "INVALIDCREDENTIALS", "message": "Failed validation with credentialType: msDynamics due to error: 'Request to backend service failed. Response from web service: {\"error\":\"invalidclient\",\"errordescription\":\"AADSTS7000218: The request body must contain the following parameter: 'clientassertion' or 'clientsecret'.\\r\\nTrace ID: 4dbeb6a2-7db0-4338-8c0d-4ea5c46c7200\\r\\nCorrelation ID: 00c83287-77ab-41d4-8335-b0a013b7893f\\r\\nTimestamp: 2019-09-03 07:51:56Z\",\"errorcodes\":[7000218],\"timestamp\":\"2019-09-03 07:51:56Z\",\"traceid\":\"4dbeb6a2-7db0-4338-8c0d-4ea5c46c7200\",\"correlationid\":\"00c83287-77ab-41d4-8335-b0a013b7893f\",\"error_uri\":\"https://login.microsoftonline.com/error?code=7000218\"} [null]' [0e764ac0-47f5-4494-b393-bfa3822248c7]", "messageParams": {}, "details": [], "errors": [] } ] }

    I have checked the Integration Credentials several times and they are ok. What could be the cause?

    Thanks

    Jason_Mathison | 2019-09-03 12:53:34 UTC | #2

    Hi Adrian_Santamaria,

    This looks like buggy behavior, which can't really be handled on the Developer Forum. Please open up a support case with Customer Care for this. If you already have a case open for this, please post the case ID.

    --Jason

    Adrian_Santamaria | 2019-09-03 14:12:17 UTC | #3

    Thank you for your response Jason. I have opened a new support case. Its ID is 5000d00001VYoxYAAT

    Adrian_Santamaria | 2019-09-04 14:45:06 UTC | #4

    The problem has been solved by changing the "allowPublicClient" flag to true in the Azure app Auth configuration.

    Thank you! :grin:

    system | 2019-10-05 14:45:12 UTC | #5

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 5939



Related Content