-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Authentication Issue with Oatuh API #54
Comments
hi @edanhauon feels like this error is coming from adal not from DynamicsWebApi. I would ask this question here. |
@edanhauon did you figure out the issue? or do you still need help? It would be better if you could post a sample of your code that acquires token. 401 is an authentication issue and the DynamicsWebApi does not retrieve it, you'll need to use adal to acquire it. |
Hi I actually used the EXACT piece of first sample code from the documentation. Edan. |
@edanhauon maybe this will help. Please make sure that you are using a correct authentication scenario in your Azure AD. |
Closing due to inactivity. |
Hi,
Getting an 401 when trying to access the API:
message:"Get Token request returned http error: 401 and server response: {"error":"invalid_client","error_description":"AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret'.\r\nTrace ID: \r\nCorrelation ID: \r\nTimestamp: 2019-07-18 14:46:12Z","error_codes":[7000218],"timestamp":"2019-07-18 14:46:12Z","trace_id":"","correlation_id":""}"
Would appreciate your help.
Edan.
The text was updated successfully, but these errors were encountered: