Click HERE to see how Saviynt Intelligence is transforming the industry. |
10/23/2024 11:58 AM
I'm working on configuring a REST API call to PowerAutomate as part of our Entra connector. This will function as a very simple call in our UpdateAccountJSON code. I am trying to test this piece of our design by itself currently, so my UpdateAccountJSON looks like this:
{
"call": [
{
"name": "call1",
"connection": "AzureADProvisioning",
"url": "https://prod-55.westus.logic.azure.com:443/workflows/REMOVED/triggers/manual/paths/invoke?&api-version=2016-06-01&sp=/triggers/manual/run&sv=1.0&sig=REMOVED",
"httpMethod": "POST",
"httpParams": "{\"parameter1\":\"email@email.com\"}",
"httpHeaders": {
"Authorization": "${access_token}",
"Content-Type": "application/json"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200,
202,
201,
204,
205
]
}
}
]
}
This API call kicks off a PowerAutomate flow that accepts parameter1's value of an email address and it then generates an email to that address. There is actually no authentication or authorization on the flow as of now (for testing). I can call this flow perfectly from POSTMAN as a POST operation with those query parameters. However, in Saviynt I cannot seem to call this API. Every time I make this call I get the following result:
Task Response: {auditDetails":{"call1":[{"headers":null message:"" statusCode:null description:null status:"Failed"} {"headers":null message:"" statusCode:null description:null status:"Failed"}]} call1:{"headers":null message:"" statusCode:null description:null status:"Failed"}}"
Through testing I have come to realize that if I remove the api-version query parameter, I can reveal a different error:
{"headers":null,"message":{"error":{"code":"MissingApiVersionParameter","message":"The api-version query parameter (?api-version=) is required for all requests."}},"statusCode":400,"description":null,"status":"Failed"}
I am unsure why when the entire URL is passed I'm getting essentially a null response. It seems Saviynt is not actually calling the API properly. Any thoughts here?
10/23/2024 12:23 PM
@BrandonLucas_BF try hardcoding token once .. ideally it should work .. give it a short.
10/23/2024 12:26 PM
Can you clarify what you mean?
One test I did was to embed the URL into an account customproperty (since I'm testing using UpdateAccount JSON). I got the same result.