garima | 2021-03-15 07:18:01 UTC | #1
hi I am trying to generate token by using webservices data action integration with azure AD , but getting error :- { "message": "The requested resource was not found.", "code": "not.found", "status": 404, "messageParams": {}, "contextId": "b8f2af6a-f727-41a7-b090-418b38220f8c", "details": [ { "errorCode": "ACTION.REMOTEENDPOINT" } ], "errors": [ { "message": "REST call for action execute failed. Message:Request to backend service failed. Response from web service: [b8f2af6a-f727-41a7-b090-418b38220f8c]", "code": "NOTFOUND", "status": 404, "messageParams": {}, "details": [], "errors": [] } ] }
where could it be going wro ng?
Jason_Mathison | 2021-03-15 14:05:47 UTC | #2
The first thing is to look at the results of resolving the URL and see if it is what you expect.
Jerome.Saint-Marc | 2021-03-15 14:33:38 UTC | #3
I am not expert in Azure AD but I can see that your Data Action - Request Configuration - Request Body Template (second set of screenshot) is incorrectly formatted. It doesn't match what you are sending in Postman.
1 - In Postman (first set of screenshot), you have defined 4 parameters in the body: client_id, client_secret, grant_type and scope In the Data Action - Request Configuration, you are using clientId, clientSecret, grantType as the parameter names. You must use the same parameter names than what you have in Postman. I don't think that it is necessary to escape clientId and clientSecret values. Not sure about scope.
So it should be (Request Body Template) something like this: client_id=${credentials.clientId}&client_secret=${credentials.clientSecret}&grant_type=client_credentials&scope=$esc.url(${credentials.scope})
2) As you are sending the clientId and the clientSecret in the request body, I doubt that you need to keep the Authorization header. If you don't have that header set in your Postman request, then remove the Authorization header from the Data Action - Request Configuration.
You can then try again your OAuth request. If ever there is an issue, you might try to add another Header name: "Transfer-Encoding", Header value: "buffered" as described here.
Regards,
garima | 2021-03-16 11:59:46 UTC | #4
Thanks . the solution worked :slight_smile:
however when I am aopying the same custom Auth data action and trying to add contracts to the copied one , I am getting authentication error :-
- Perform authentication
{ "message": "There was an issue validating the credentials.", "code": "invalid.credentials", "status": 400, "entityName": "basicAuth", "messageParams": {}, "contextId": "7ad3c9d3-73e8-4ebf-bcd1-7f4bd3587a8e", "details": [ { "errorCode": "ACTION.AUTHENTICATION" } ], "errors": [ { "message": "REST call for action execute failed. Message:Request to backend service failed. To see error details, use test mode to execute the action, or execute request in Postman or other REST tools. [7ad3c9d3-73e8-4ebf-bcd1-7f4bd3587a8e]", "code": "INVALID_CREDENTIALS", "status": 404, "messageParams": {}, "details": [], "errors": [] } ] }
Jerome.Saint-Marc | 2021-03-18 19:00:29 UTC | #5
Hello,
You are not supposed to make a copy of the "Custom Auth" data action. In "Admin - Integrations - Actions", you just need to create a new data action (clicking on the "+ Add Action" button), that you will connect to your Web Services Data Action Integration (on which you have configured the credentials).
You new data action will automatically inherit/point to the "Custom Auth" data action. When editing the action, you will see a "User Defined (OAuth" link, under Authentication Types (Summary tab) and Authentication (Setup tab - Configuration - Request).
Make sure that your Custom Auth data action is published.
Regards,
system | 2021-04-18 19:00:31 UTC | #6
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: 10273