I have an OpenAPI definition (Swagger) for an anonymous endpoint (authenticated by providing a licenseId and appId as header values). This OpenAPI definition works with Logic Apps and Nintex Workflow Cloud, but not with Flow. I imported the defintiion, and set security to none (same exact steps as Logic Apps), all of the operations are correctly identified, but when I test it I get odd/incorrect results.
The request url should be https://dev-api.elasticocr.com/v1.0/jobs/{jobid}, but Flow is sending it to msmanaged-na.azure-apim.net
Request
Url:
https://msmanaged-na.azure-apim.net/apim/elasticocr.20.2d.20dev.5fae991b2e953c45e5.5f0447122807b1e5ce/81fe0440-986b-4d43-aada-2e59-ade12221/jobs/[jobid]
Headers:
{
"Authorization": "Bearer {token}",
"licenseId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"appId": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy"
}
licenseId/appId removed for security purposes, but I can't figure out why it's sending the request to a different domain, and why it's including a bearer token given that the API is technically anonymous. We do not see these issues in Logic Apps, only in Flow.
Security is correctly configured:
As a result of the wrong request URL, the response is obviously also incorrect:
{
"error": "{\r\n \"code\": 404,\r\n \"message\": \"Unable to match incoming request to an operation.\",\r\n \"source\": \"msmanaged-na.azure-apim.net\",\r\n \"path\": \"\",\r\n \"clientRequestId\": \"53c6068c-9566-4b87-8311-c117-0304008c\"\r\n}"
}
I have seen a few reports that msmanaged-na.azure-apim.net/apim is used as a proxy if the API is protected by OAuth, but in our case it obviously isn't and security is set to none, so I'm baffled as to what's going on here. Any advice or insight is appreciated.
